cve.bz

CVE-2026-29036 davegamble cjson

8.7 highEPSS 0.4%

High (8.7) in davegamble cjson. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
cJSON versions 1.5.0 through 1.7.19 contain an incorrectly-resolved name or reference vulnerability in the decode_pointer_inplace() function within cJSON_Utils.c that allows unauthenticated attackers to cause JSON Patch operations to target wrong object keys by supplying crafted JSON Pointer escape sequences (~0 or ~1) in patch paths. Attackers can submit malicious RFC 6902 JSON Patch input to applications using cJSONUtils_ApplyPatches() or cJSONUtils_ApplyPatchesCaseSensitive() to silently corrupt data or delete unintended keys, potentially bypassing authorization controls in applications that rely on JSON Patch for access-controlled data modification.

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 39th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-08-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-706 Use of Incorrectly-Resolved Name or Reference
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-29036 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-29036?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-29036?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-29036 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
DaveGamble cJSONfrom 1.5.0 through 1.7.19

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14cjsonno fix listedDEBIAN-CVE-2026-29036
Ubuntu26.04:LTS, 26.10, Pro:20.04:LTS and 2 morecjsonno fix listedUBUNTU-CVE-2026-29036

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as an Important severity flaw because an unauthenticated remote attacker could compromise application data integrity by silently altering or deleting restricted parameters without proper authorization. Within Red Hat environments, overall exposure depends on whether higher-level services process RFC 6902 patch requests from untrusted network sources. Although core Red Hat Enterprise Linux distributions do not ship this component directly, affected layered services that rely on patch evaluation routines face significant integrity risks when processing malformed escape characters.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 8rpm-ostreeNot affected
Red Hat Hardened ImageschunkahNot affected
Red Hat OpenShift Container Platform 4rpm-ostreeNot affected
Red Hat Satellite 6cjsonAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-29036.

Attack patterns (CAPEC)

  • CAPEC-48 Passing Local Filenames to Functions That Expect a URL Likelihood: High · Severity: High
  • CAPEC-159 Redirect Access to Libraries Likelihood: High · Severity: Very High
  • CAPEC-177 Create files with the same name as files protected with a higher classification Severity: Very High
  • CAPEC-641 DLL Side-Loading Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON