Netatalk memory corruption in afpd DHX2 login
- Exploited
- No known exploitation
- Fix
- Fixed in 4.5.1
- Who is exposed
- Not reported
Summary
Netatalk's afpd file server has a memory-handling flaw in its DHX2 and DHX2-PAM login methods that can be reached remotely, without logging in, when those methods are enabled. An attacker can repeat a login step to crash a privileged afpd worker, and the memory errors could plausibly help in building code execution, though that was not demonstrated.
Written by a model
Original description
Netatalk is a Free and Open Source file server suite for Unix-like operating systems. From 2.0.0 until 4.5.1, the DHX2 and DHX2-PAM authentication state machine in etc/uams/uams_dhx2_pam.c permits logincont1 to be invoked again with the same FPLoginCont retID after it has released the global gcry_mpi_t Ra object. When DHX2 or DHX2PAM is enabled in the UAM list, a remote attacker without valid AFP credentials can repeat the first continuation step, causing gcry_mpi_powm to dereference the freed Ra value and gcry_mpi_release to free it again in a privileged afpd worker. The demonstrated result is a repeatable pre-authentication worker crash, and the use-after-free and double-free provide a plausible allocator exploitation primitive although code execution was not demonstrated. This issue is fixed in version 4.5.1.
What to do
Upgrade to a fixed version: 4.5.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-62318 (Netatalk: afpd DHX2 UAM pre-authentication use-after-free and double-free via repeated FPLoginCont), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-62318 (entry last updated 2026-11-20):
Affected:
- Netatalk netatalk: from 2.0.0, fixed in 4.5.1
Fixed versions: 4.5.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-62318 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-62318 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Netatalk/netatalk/security/advisories/GHSA-5wp7-47vr-j2mh
- https://github.com/Netatalk/netatalk/commit/c2ea1f459d85c17a43378ea85a19912ce5eb3dd1
- https://github.com/Netatalk/netatalk/commit/fe0a2b72a64b4f0291fa1ca8c049f56b5081d65a
- https://github.com/Netatalk/netatalk/releases/tag/netatalk-4-5-1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-62318
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-62318"}.Affected versions
- Netatalk netatalkFrom 2.0.0 · fixed in 4.5.1
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · Netatalk/netatalk · Advisory GHSA-5wp7-47vr-j2mh |
| CVE record 1Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-62318 |
| Other links 3 | |
| Repository | GitHub · Netatalk/netatalk · Commit c2ea1f45 |
| Repository | GitHub · Netatalk/netatalk · Commit fe0a2b72 |
| Repository | GitHub · Netatalk/netatalk · Release netatalk-4-5-1 |
Questions about CVE-2026-62318
Is CVE-2026-62318 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-62318?
netatalk: from 2.0.0 before 4.5.1.
Source: cve.now feed data
How do I fix CVE-2026-62318?
Upgrade to a fixed version: 4.5.1.
Source: cve.now feed data
Related
- CVE-2026-62320Netatalk: afpd unauthenticated DSI request smuggling via silent dsi_len truncation in dsi_tcp_open()
- CVE-2026-62321Netatalk: afpd Spotlight RPC heap-buffer-overflow in nested sl_pack_filemeta() marshalling
- CVE-2026-45354Netatalk: Pre-auth DSI Protocol Desync via dsi_code/dsi_doff Union
- CVE-2026-45698Netatalk has Integer Underflow → Stack Buffer Overflow in deletedir()
- CVE-2026-45699Netatalk has Integer Underflow → Stack Buffer Overflow in copydir()
- CVE-2026-62319Netatalk: afpd authenticated DSIWrite request smuggling due to missing dsi_doff <= dsi_len validation
No corrections so far. Something wrong on this page? Report an error.