CVE-2026-7835 json
Format string argument mismatch
published 2026-05-21 5 mo ago modified 2026-07-23 3 mo ago also EUVD-2026-31223
- cvss
- 3.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
A format string argument mismatch in Netatalk 3.0.3 through 4.4.2 allows a remote authenticated attacker to cause a minor denial of service via crafted input that triggers incorrect format string processing.
Patch / fix
- Netatalk Netatalk 4.5.0
- netatalk Debian 14 4.5.0~ds-1
debian advisories DEBIAN-CVE-2026-7835
- netatalk Alpine 3.24 4.5.0-r0
alpine advisories ALPINE-CVE-2026-7835
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-7835 updated cvss 3.1
netatalk: Netatalk: Denial of Service via format string argument mismatch
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L |
Affected products
- Netatalk Netatalk
Classification
- Weakness
-
- CWE-134 Use of Externally-Controlled Format String
References
-
netatalk.io
/security/CVE-2026-7835
vendor-advisory
Sources
- CVE List CVE-2026-7835
- NVD CVE-2026-7835
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.