Process crash via inconsistent token-tree traversal
Published Oct 13, 2026 · Updated Oct 13, 2026
Out-of-bounds reading in JSMN's jsondump example at commit 25647e6 allows attackers to crash the process via malformed JSON input. Non-strict jsmn_parse assigns child counts to non-container tokens, and dump() trusts those counts while traversing beyond the token array. Exposure requires untrusted input reaching this example or equivalent traversal code in non-strict mode; the parser itself remains in bounds.
Summary
What happened
Out-of-bounds reading in JSMN's jsondump example at commit 25647e6 allows attackers to crash the process via malformed JSON input. Non-strict jsmn_parse assigns child counts to non-container tokens, and dump() trusts those counts while traversing beyond the token array. Exposure requires untrusted input reaching this example or equivalent traversal code in non-strict mode; the parser itself remains in bounds.
The record
- CVE
- CVE-2026-95117
- Published
- Oct 13, 2026
- Updated
- Oct 13, 2026
- Vendor
- Serge Zaitsev
- Product
- JSMN
- Classifications
- T1499
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 13, 2026CVE publishedPublication date reported by the CVE source.
- Oct 13, 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=n/a
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started