Quick answers
- Is CVE-2026-7835 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-7835 being exploited in the wild.
- How severe is CVE-2026-7835?
- Low severity, with a CVSS score of 3.1, published 21 May 2026.
- Which products and versions are affected?
- Netatalk Project Netatalk 3.0.3 through 4.4.2.
- Is there a fix for CVE-2026-7835?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-7835 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-7835?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A format string argument mismatch (CWE-134) exists in Netatalk versions 3.0.3 through 4.4.2 within a logging statement located on an allocation-failure code path. The vulnerability occurs when a log message expects a string argument that is not provided by the calling function. Because the format string itself is static and not controlled by an attacker, the issue is not exploitable for arbitrary code execution. The impact is limited to a potential application crash (Denial of Service) if the system encounters an out-of-memory state that triggers the specific logging path. The issue is resolved in version 4.5.0.
Affected products
- Netatalk Project Netatalk 3.0.3 through 4.4.2
Timeline
- 2026-05-13: disclosed: Initial disclosure date
- 2026-05-21: advisory: NVD publication date