CVE-2026-67216

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6% (49th percentile of EPSS-scored CVEs). GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
50
EG Risk 50/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.6%
EPSS %ILE
49th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 29, 2026

Last Modified

August 4, 2026

Advisory Details (3)

Auto-updated Jul 29, 2026
🔬 Proof of concept available. Fix referenced — no release confirmed yet.
generic

cJSON cJSON_Compare Exponential Complexity Denial of Service | Advisories | VulnCheck

https://www.vulncheck.com/advisories/cjson-cjson-compare-exponential-complexity-denial-of-service
generic

cJSON/cJSON.c at v1.7.19 · DaveGamble/cJSON · GitHub

https://github.com/DaveGamble/cJSON/blob/v1.7.19/cJSON.c#L3057-L3180
generic🟡 PoC Available

33 Vulnerabilities in cJSON | Joshua Rogers' Scribbles

https://joshua.hu/cjson-json-parser-cve-vulnerabilities

Vendor Advisories for CVE-2026-67216(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
cjson1.7.14-1 ... 1.7.19-2 (16 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
cjson1.7.15-1 ... 1.7.19-2 (16 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
cjson1.7.18-3.1, 1.7.18-3.1+deb13u1, 1.7.18-4, 1.7.19-1, 1.7.19-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
cjson1.7.18-3.1, 1.7.18-4, 1.7.19-1, 1.7.19-2
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 98× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 247 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:13 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-07 00:01 UTCEG score recompute
  5. 2026-10-07 00:01 UTCVendor advisory
  6. 2026-10-07 00:01 UTCGHSA enrichment
  7. 2026-10-06 15:18 UTCEPSS rescore
  8. 2026-10-05 20:53 UTCEG score recompute
  9. 2026-10-05 20:53 UTCVendor advisory
  10. 2026-10-05 20:53 UTCGHSA enrichment
  11. 2026-10-05 17:43 UTCEPSS rescore
  12. 2026-10-05 02:37 UTCEG score recompute
  13. 2026-10-05 02:37 UTCVendor advisory
  14. 2026-10-05 02:37 UTCGHSA enrichment
  15. 2026-10-04 23:22 UTCEPSS rescore
  16. 2026-10-04 07:02 UTCEG score recompute
  17. 2026-10-04 07:02 UTCVendor advisory
  18. 2026-10-04 07:02 UTCGHSA enrichment
  19. 2026-10-03 14:26 UTCEPSS rescore
  20. 2026-10-02 17:58 UTCEG score recompute
  21. 2026-10-02 17:58 UTCVendor advisory
  22. 2026-10-02 17:58 UTCGHSA enrichment
  23. 2026-10-02 17:56 UTCEPSS rescore
  24. 2026-10-01 19:50 UTCEPSS rescore
  25. 2026-10-01 15:54 UTCVendor advisory
Show 75 more
  1. 2026-10-01 15:54 UTCGHSA enrichment
  2. 2026-10-01 03:36 UTCEG score recompute
  3. 2026-10-01 03:36 UTCVendor advisory
  4. 2026-10-01 03:36 UTCGHSA enrichment
  5. 2026-09-30 15:03 UTCEPSS rescore
  6. 2026-09-29 07:36 UTCEG score recompute
  7. 2026-09-29 07:36 UTCVendor advisory
  8. 2026-09-29 07:36 UTCGHSA enrichment
  9. 2026-09-28 13:52 UTCEPSS rescore
  10. 2026-09-28 03:17 UTCEG score recompute
  11. 2026-09-28 03:17 UTCVendor advisory
  12. 2026-09-28 03:17 UTCGHSA enrichment
  13. 2026-09-27 13:48 UTCEPSS rescore
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-25 05:41 UTCEG score recompute
  16. 2026-09-25 05:41 UTCVendor advisory
  17. 2026-09-25 05:41 UTCGHSA enrichment
  18. 2026-09-24 10:09 UTCVendor advisory
  19. 2026-09-24 10:09 UTCGHSA enrichment
  20. 2026-09-23 21:50 UTCEG score recompute
  21. 2026-09-23 21:50 UTCVendor advisory
  22. 2026-09-23 21:50 UTCGHSA enrichment
  23. 2026-09-23 17:54 UTCEPSS rescore
  24. 2026-09-23 04:12 UTCEG score recompute
  25. 2026-09-23 04:12 UTCVendor advisory
  26. 2026-09-23 04:12 UTCGHSA enrichment
  27. 2026-09-22 15:49 UTCEG score recompute
  28. 2026-09-22 15:49 UTCVendor advisory
  29. 2026-09-22 15:49 UTCGHSA enrichment
  30. 2026-09-20 20:16 UTCEPSS rescore
  31. 2026-09-20 00:23 UTCEG score recompute
  32. 2026-09-20 00:23 UTCVendor advisory
  33. 2026-09-20 00:23 UTCGHSA enrichment
  34. 2026-09-19 04:55 UTCEG score recompute
  35. 2026-09-19 04:55 UTCVendor advisory
  36. 2026-09-19 04:55 UTCGHSA enrichment
  37. 2026-09-18 19:28 UTCEPSS rescore
  38. 2026-09-18 15:17 UTCVendor advisory
  39. 2026-09-18 15:17 UTCGHSA enrichment
  40. 2026-09-18 01:42 UTCEG score recompute
  41. 2026-09-18 01:42 UTCVendor advisory
  42. 2026-09-18 01:42 UTCGHSA enrichment
  43. 2026-09-17 01:36 UTCEG score recompute
  44. 2026-09-17 01:36 UTCVendor advisory
  45. 2026-09-17 01:36 UTCGHSA enrichment
  46. 2026-09-16 14:08 UTCEPSS rescore
  47. 2026-09-16 05:49 UTCEG score recompute
  48. 2026-09-16 05:49 UTCVendor advisory
  49. 2026-09-16 05:49 UTCGHSA enrichment
  50. 2026-09-16 05:15 UTCEPSS rescore
  51. 2026-09-15 08:07 UTCEG score recompute
  52. 2026-09-15 08:07 UTCVendor advisory
  53. 2026-09-15 08:07 UTCGHSA enrichment
  54. 2026-09-14 10:14 UTCVendor advisory
  55. 2026-09-14 10:14 UTCGHSA enrichment
  56. 2026-09-13 21:45 UTCEG score recompute
  57. 2026-09-13 21:45 UTCVendor advisory
  58. 2026-09-13 21:45 UTCGHSA enrichment
  59. 2026-09-13 09:27 UTCVendor advisory
  60. 2026-09-13 09:27 UTCGHSA enrichment
  61. 2026-09-12 21:08 UTCEG score recompute
  62. 2026-09-12 21:08 UTCVendor advisory
  63. 2026-09-12 21:08 UTCGHSA enrichment
  64. 2026-09-12 08:49 UTCVendor advisory
  65. 2026-09-12 08:49 UTCGHSA enrichment
  66. 2026-09-11 20:30 UTCEG score recompute
  67. 2026-09-11 20:30 UTCVendor advisory
  68. 2026-09-11 20:30 UTCGHSA enrichment
  69. 2026-09-11 14:53 UTCEPSS rescore
  70. 2026-09-11 09:37 UTCEPSS rescore
  71. 2026-09-11 08:11 UTCGHSA enrichment
  72. 2026-09-10 19:52 UTCEG score recompute
  73. 2026-09-10 19:52 UTCGHSA enrichment
  74. 2026-09-10 07:14 UTCGHSA enrichment
  75. 2026-09-09 07:50 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-67216?
CVE-2026-67216 is a high vulnerability published on July 29, 2026. cJSON through 1.7.19 contains an inefficient algorithmic complexity flaw in cJSONCompare(). 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…
When was CVE-2026-67216 disclosed?
CVE-2026-67216 was first published on July 29, 2026, with the most recent update on August 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67216 actively exploited?
CVE-2026-67216 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67216?
CVE-2026-67216 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-67216?
A fix for CVE-2026-67216 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-67216 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-67216

Explore →

Is Your Infrastructure Affected by CVE-2026-67216?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs