CVE-2026-67215

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-29. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 29, 2026

Last Modified

August 4, 2026

Advisory Details (4)

Auto-updated Jul 29, 2026
Patch available.
Web page

cJSON JSON Patch copy/add Uncontrolled Recursion Stack Exhaustion | Advisories | VulnCheck

https://www.vulncheck.com/advisories/cjson-json-patch-copy-add-uncontrolled-recursion-stack-exhaustion
Web page

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

https://github.com/DaveGamble/cJSON/blob/v1.7.19/cJSON_Utils.c#L906-L940
Web page

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

https://github.com/DaveGamble/cJSON/blob/v1.7.19/cJSON.c#L253-L261
Web page

33 Vulnerabilities in cJSON | Joshua Rogers' Scribbles

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

Vendor Advisories for CVE-2026-67215(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 14× in last 7d / 89× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 261 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 161 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-67215?
CVE-2026-67215 is a high-severity vulnerability; its CVE record was published on July 29, 2026. cJSON through 1.7.19 is vulnerable to uncontrolled recursion leading to stack exhaustion when an untrusted RFC 6902 JSON Patch is applied via cJSONUtilsApplyPatches() or cJSONUtilsApplyPatchesCaseSensitive(). A patch containing add and copy operations grafts duplicated subtrees to amplify document…
When was CVE-2026-67215 made public?
CVE-2026-67215 was made public on July 25, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 29, 2026. EchelonGraph's copy of the record carries a last-modified date of August 4, 2026; the record at its source may have been updated since.
Is CVE-2026-67215 actively exploited?
CVE-2026-67215 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67215?
CVE-2026-67215 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-67215?
A fix for CVE-2026-67215 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67215 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-67215

Explore →

Is Your Infrastructure Affected by CVE-2026-67215?

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

Book a Demo →Browse All CVEs