CVE-2026-29036 DaveGamble CVE debrief

Who should care

Defenders responsible for applications using cJSON, particularly those relying on JSON Patch for access-controlled data modification, should assess exposure and prioritize verification and mitigation.

Why it matters

CVE-2026-29036 is a high-severity vulnerability in cJSON that allows unauthenticated attackers to cause JSON Patch operations to target wrong object keys, potentially leading to data corruption or deletion and bypassing authorization controls. Defenders should prioritize verifying the vulnerability in their inventory, assessing exposure, and applying patches or mitigations as available.

• Data corruption or deletion due to targeted JSON Patch operations
• Potential bypass of authorization controls in applications using JSON Patch
• Verification of vulnerability in inventory and exposure assessment
• Prioritization of patching or mitigation efforts

Technical summary

The vulnerability is caused by an incorrectly-resolved name or reference issue in the decode_pointer_inplace() function within cJSON_Utils.c. This allows attackers to submit malicious RFC 6902 JSON Patch input to applications using cJSONUtils_ApplyPatches() or cJSONUtils_ApplyPatchesCaseSensitive(), potentially bypassing authorization controls. Affected product deployments should be verified, and patches or mitigations applied as available to prevent silent data corruption or deletion of unintended keys. Defenders should prioritize verifying the vulnerability in their inventory, assessing exposure, and applying patches or mitigations as available.

Defensive priority

Defenders should prioritize verifying the vulnerability in their inventory, assessing exposure, and applying patches or mitigations as available.

Recommended defensive actions

• Verify the vulnerability in your inventory
• Assess exposure and apply patches or mitigations as available
• Monitor for potential data corruption or deletion
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. However, the corpus does not establish versions, exploitation, impact, or remediation, which require verification from the supplied official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.