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 65% 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 — 3 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
35%
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.

Data Freshness Timeline

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

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

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 64.6% 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