Skip to main content
VulnerabilityPublished

CVE-2026-49390: netatalk · Improper Input Validation

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:N/I:N/A:L

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
  • >=3.0.0 <4.5.0
Fixed in
  • 4.5.0

AI-suggested

Upgrade Netatalk to version 4.5.0 or later where this issue is fixed. Until then, ensure that the server quantum value in afp.conf is within valid ranges to avoid startup failures or service disruption. Since the option is read only at startup and locally configured, careful configuration review can prevent this issue.

Description

Netatalk versions from 3.0.0 up to but not including 4.5.0 contain an improper input validation vulnerability in the getoption_int function. This flaw allows an administrator to configure an out-of-range server quantum value in afp.conf, which can cause the AFP daemon to panic at startup or disrupt DSI framing, rendering the service unavailable until the configuration is corrected and the daemon restarted. The issue is fixed in version 4.5.0.

References

Community reviews

Loading reviews…