cve.bz

CVE-2026-67215 davegamble cjson: Uncontrolled Recursion

8.7 highExploit referenceEPSS 0.7%Fix available

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

On this page
cJSON through 1.7.19 is vulnerable to uncontrolled recursion leading to stack exhaustion when an untrusted RFC 6902 JSON Patch is applied via cJSONUtils_ApplyPatches() or cJSONUtils_ApplyPatchesCaseSensitive(). A patch containing add and copy operations grafts duplicated subtrees to amplify document depth beyond the parser's nesting limit: cJSON_Delete() recurses with no depth bound, and the cJSON_Duplicate() guard CJSON_CIRCULAR_LIMIT is set to 10000, ten times the parser's 1000-level nesting limit and high enough to overflow a default thread stack. An attacker who can supply the patch document can crash the process, resulting in denial of service.

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/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:N/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 54th 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-07-29. 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-674 Uncontrolled Recursion
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-67215 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-67215?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-67215?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-67215 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 cJSONthrough 1.7.19

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14cjsonno fix listedDEBIAN-CVE-2026-67215
Ubuntu26.04:LTS, 26.10, Pro:20.04:LTS and 2 morecjsonno fix listedUBUNTU-CVE-2026-67215
Azure Linux3apparmorno fix listedAZL-94410
Azure Linux3libglvndno fix listedAZL-94437

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. 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

A denial of service vulnerability was found in cJSON. When an application applies an untrusted RFC 6902 JSON Patch document via cJSONUtils_ApplyPatches() or cJSONUtils_ApplyPatchesCaseSensitive(), a patch using add and copy operations can graft duplicated subtrees to amplify document nesting beyond the parser's limit. The subsequent unbounded recursion in cJSON_Delete() exhausts the thread stack and crashes the process.

Red Hat rates the impact of this flaw as Important. The impact is limited to availability (denial of service); there is no effect on confidentiality or integrity. Exploitation requires the application to apply an attacker-controlled JSON Patch document using the vulnerable cJSON-Utils functions; applications that do not process untrusted JSON Patch input are not affected.

The rpm-ostree component shipped in Red Hat Enterprise Linux and Red Hat OpenShift Container Platform is not affected: its 'cjson' dependency is the unrelated Rust cjson crate (a canonical-JSON serializer), not DaveGamble's C cJSON library, and it does not exercise the vulnerable code path.

Red Hat's mitigation

To reduce the risk of exploitation, do not apply RFC 6902 JSON Patch documents originating from untrusted or unauthenticated sources using cJSON's cJSONUtils_ApplyPatches() or cJSONUtils_ApplyPatchesCaseSensitive() functions. Where the JSON Patch feature is not required, avoid calling these functions on externally supplied input. Applications that must process untrusted patch documents should enforce input size and nesting-depth limits before passing data to cJSON. This issue is a design limitation in cJSON's recursive handling and has no upstream fix as of version 1.7.19.

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-67215.

Attack patterns (CAPEC)

  • CAPEC-230 Serialized Data with Nested Payloads Likelihood: Medium · Severity: High
  • CAPEC-231 Oversized Serialized Data Payloads Likelihood: Medium · Severity: High

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

References

Check your stackJSON