Skip to main content
VulnerabilityPublished

CVE-2026-49389: netatalk · Out-of-bounds Read

Affects netatalkSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.1 Low : upgrade to 4.5.0 when convenient.

Data as of 20 Nov 2026, 17:32 UTC

CVSS 3.1 base score
3.1Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.13.1
Patch
Available – fixed in 4.5.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.

What to do

Upgrade netatalk to 4.5.0.

Affected software

ProductAffectedFixed in
NetatalknetatalkAffected
  • >=2.0.0 <4.5.0
Fixed in
  • 4.5.0

AI-suggested

A patch is available and the issue is fixed in Netatalk version 4.5.0. Users should upgrade to version 4.5.0 or later to remediate this vulnerability. Since this is a cloud service, the vendor manages remediation for the cloud-hosted service; check the vendor advisory for confirmation. No additional mitigation actions are indicated.

Description

CVE-2026-49389 is an out-of-bounds read vulnerability in Netatalk versions from 2.0.0 up to but not including 4.5.0. The flaw occurs in the afp_catsearch component where an authenticated AFP client can cause the server to read stale bytes beyond the supplied request data due to improper validation of the spec_len field. The bytes read are used internally and not returned to the client. Testing did not show crashes or information disclosure. The issue is fixed in version 4.5.0.

References

Community reviews

Loading reviews…