Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-88369 Overview
CVE-2026-88369 is a buffer overflow vulnerability in the zserge/jsmn JSON parsing library at commit 25647e6. The flaw resides in the dump() function inside example/jsondump.c. An attacker supplying crafted JSON input can trigger an out-of-bounds read [CWE-125] during parsing. The issue is reachable over the network when applications expose the example parser to untrusted input.
Critical Impact
Attackers can trigger an out-of-bounds memory read in jsondump by submitting malformed JSON, resulting in information disclosure, process crashes, or further memory corruption.
Affected Products
- zserge jsmn JSON parser at commit 25647e6
- Applications bundling example/jsondump.c from the affected commit
- Downstream forks that inherit the vulnerable dump() routine
Discovery Timeline
- 2026-09-24 - CVE-2026-88369 published to the National Vulnerability Database (NVD)
- 2026-09-25 - Last updated in NVD database
Technical Details for CVE-2026-88369
Vulnerability Analysis
The jsmn library is a minimalist JSON parser written in C and widely embedded in resource-constrained projects. The vulnerability affects the example consumer example/jsondump.c, specifically the dump() function that recursively walks parsed JSON tokens. The function does not adequately validate token boundaries against the length of the input buffer before dereferencing token offsets. Crafted JSON causes the parser to read memory outside the intended bounds of the token or input array. The weakness is classified under [CWE-125] Out-of-bounds Read.
Root Cause
The root cause is missing bounds validation between the token metadata produced by jsmn_parse() and the actual length of the JSON input passed to dump(). When tokens reference offsets or sizes that exceed the input buffer, the recursive dumper walks past valid memory. The example code trusts token descriptors instead of re-validating them against buffer length.
Attack Vector
Exploitation requires an attacker to deliver crafted JSON to any service or utility that invokes the vulnerable dump() routine. No authentication or user interaction is required. The impact depends on how the embedding application processes the output, ranging from memory disclosure to denial of service via segmentation faults. See the GitHub Issue Discussion for technical details and reproducer behavior reported upstream.
Detection Methods for CVE-2026-88369
Indicators of Compromise
- Unexpected crashes or SIGSEGV signals in processes linking the jsmn example jsondump code
- Anomalous memory contents or truncated output written by services that dump parsed JSON
- Repeated malformed JSON payloads targeting endpoints that invoke jsmn_parse() followed by dump()
Detection Strategies
- Perform source-code audits for inclusion of example/jsondump.c at commit 25647e6 across build pipelines
- Run fuzzing campaigns against dump() with mutated token arrays and oversized input samples
- Enable AddressSanitizer (ASan) in CI builds to catch out-of-bounds reads during regression testing
Monitoring Recommendations
- Alert on process termination events and core dumps from binaries that embed jsmn
- Log and inspect inbound JSON payloads that produce parser errors or abnormal response sizes
- Track dependency manifests and software bill of materials (SBOM) entries referencing the affected commit
How to Mitigate CVE-2026-88369
Immediate Actions Required
- Remove or isolate example/jsondump.c from production builds; the file is intended as a demonstration, not a hardened component
- Replace calls to the vulnerable dump() with a hardened equivalent that validates every token offset against input length
- Restrict network exposure of any service that invokes the example dumper on untrusted JSON
Patch Information
No official patched release is referenced in the NVD entry at publication time. Monitor the upstream repository and the GitHub Issue Discussion for maintainer response and remediation guidance. Rebuild dependent software once a fixed commit is published.
Workarounds
- Validate token start and end offsets against the JSON input length before dereferencing in any recursive walker
- Reject JSON inputs that exceed application-defined size limits before parsing
- Compile affected binaries with -fsanitize=address or stack protection flags in test environments to surface boundary violations early
# Configuration example: build with runtime checks to detect OOB reads
gcc -O2 -Wall -fsanitize=address -fno-omit-frame-pointer \
-o jsondump example/jsondump.c jsmn.c
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

