cve.bz

CVE-2026-67216 davegamble cjson: Inefficient Algorithmic Complexity

8.2 highExploit referenceEPSS 0.6%Fix available

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

On this page
cJSON through 1.7.19 contains an inefficient algorithmic complexity flaw in cJSON_Compare(). When comparing objects, the function recurses into each shared subtree twice, once in each direction, with no depth guard, making the running time exponential in nesting depth. A small, deeply nested document of a few hundred bytes (depth around 40) compared for equality consumes hours of CPU, and the cost roughly doubles with each additional level of nesting. An application that calls cJSON_Compare() on attacker-influenced JSON that is structurally equal to a reference document is exposed to a denial-of-service condition.

Severity

CVSS 4.0

8.2 high
CVSS:4.0/AV:N/AC:L/AT:P/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.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 52nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-07-30. 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-407 Inefficient Algorithmic Complexity
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-67216 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-67216?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-67216?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-67216 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-67216
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 2 moremapcacheno fix listedUBUNTU-CVE-2026-67216
Ubuntu26.04:LTS, 26.10cjson, iperf3, mapcache and 1 moreno fix listedUBUNTU-CVE-2026-67216
UbuntuPro:16.04:LTS, Pro:18.04:LTSiperf3no fix listedUBUNTU-CVE-2026-67216
UbuntuPro:20.04:LTS, Pro:22.04:LTS, Pro:24.04:LTScjson, iperf3no fix listedUBUNTU-CVE-2026-67216
Azure Linux3apparmorno fix listedAZL-94407

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

Red Hat's statement

While upstream sources rate this flaw as High impact (CVSSv4 8.2), Red Hat evaluates this issue as Moderate impact (CVSS 5.9). This reflects a higher Attack Complexity (AC:H) and an impact strictly isolated to Availability (A:H), with zero effect on Confidentiality or Integrity (C:N, I:N).

Exploitation is narrowly constrained: an attacker cannot trigger resource exhaustion simply by submitting a deeply nested document to a standard JSON ingestion endpoint. The host application must explicitly pass the input into cJSON_Compare() against a structurally matching reference document. Applications that only parse, validate, or serialize JSON without invoking object equality comparisons are completely unaffected by this algorithmic complexity flaw.

When triggered, the resulting exponential running time leads strictly to thread CPU starvation. It does not cause stack exhaustion crashes, memory corruption, or arbitrary code execution.

Red Hat's mitigation

Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.

ProductPackageStateAdvisory
Red Hat Hardened ImageschunkahNot affected
Red Hat Satellite 6cjsonNot affected
Red Hat Satellite 6satellite:el8/cjsonNot affected

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

References

Check your stackJSON