Wrong-key modification via JSON Pointer misdecoding
Published Aug 11, 2026 · Updated Aug 11, 2026
Incorrect JSON Pointer resolution in cJSON 1.5.0 through 1.7.19 allows remote attackers to modify unintended object keys via JSON Patch input. In decode_pointer_inplace(), the ~1 branch writes a slash to decoded_string[1] instead of the current output position, silently resolving crafted paths to the wrong key. Exposure requires an application to pass attacker-controlled patches to the affected helpers; exploitation corrupts or deletes unintended data, while authorization impact depends on application logic.
Summary
What happened
Incorrect JSON Pointer resolution in cJSON 1.5.0 through 1.7.19 allows remote attackers to modify unintended object keys via JSON Patch input. In decode_pointer_inplace(), the ~1 branch writes a slash to decoded_string[1] instead of the current output position, silently resolving crafted paths to the wrong key. Exposure requires an application to pass attacker-controlled patches to the affected helpers; exploitation corrupts or deletes unintended data, while authorization impact depends on application logic.
The record
- CVE
- CVE-2026-29036
- Published
- Aug 11, 2026
- Updated
- Aug 11, 2026
- Vendor
- cJSON Project
- Product
- cJSON
- Classifications
- CWE-706, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 11, 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=1.5.0 <=1.7.19
What conditions does exploitation require?
What is affected?
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
- cJSON issue 977 reproduction programproof of concept · demonstrated
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