Server crash via missing logging argument
Published May 21, 2026 · Updated May 21, 2026
A logging format mismatch in Netatalk 3.0.3 through 4.4.2 allows remote authenticated users to crash the server under low-memory conditions. An allocation-failure logging statement uses a fixed format string that expects a string argument, but the call does not supply that argument. The path requires authentication and an allocation failure; the format string is not attacker-controlled, and impact is limited to a possible process crash.
Summary
What happened
A logging format mismatch in Netatalk 3.0.3 through 4.4.2 allows remote authenticated users to crash the server under low-memory conditions. An allocation-failure logging statement uses a fixed format string that expects a string argument, but the call does not supply that argument. The path requires authentication and an allocation failure; the format string is not attacker-controlled, and impact is limited to a possible process crash.
The record
- CVE
- CVE-2026-7835
- Published
- May 21, 2026
- Updated
- May 21, 2026
- Vendor
- Netatalk
- Product
- Netatalk
- Classifications
- CWE-134, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 2026CVE publishedPublication date reported by the CVE source.
- May 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0.3 <=4.4.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo