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.4%, top 63% of all CVEs by exploit prediction. 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 a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.5(medium)
EG Risk
50(Track)
EG Risk 50/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

July 29, 2026

Last Modified

August 4, 2026

Advisory Details (3)

Auto-updated Jul 29, 2026
🔬 Proof of concept available. No patch 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(1)

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 rangeFixed inDependents
cjson1.7.14-1 ... 1.7.19-2 (16 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
cjson1.7.15-1 ... 1.7.19-2 (16 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
cjson1.7.18-3.1, 1.7.18-3.1+deb13u1, 1.7.18-4, 1.7.19-1, 1.7.19-2——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
cjson1.7.18-3.1, 1.7.18-4, 1.7.19-1, 1.7.19-2——

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 30× in last 7d / 102× 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 189 total refreshes for this CVE.

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

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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 63.5% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67216, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs