CVE-2026-67217

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-07-29. A secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.3Exploit: 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 applies RFC 6902 JSON Patch operations non-atomically in apply_patch() in cJSON_Utils.c. For a replace operation that is missing its value member, or a move operation whose destination path cannot be resolved, the existing target member is detached and deleted before the operation is fully validated, so the target document is mutated while cJSONUtils_ApplyPatches() or cJSONUtils_ApplyPatchesCaseSensitive() returns a failure status. An attacker who can supply the patch document can destroy addressable members of the target document even though the API reports that the patch failed, defeating the all-or-nothing behavior callers rely on to reject bad patches.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/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
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend 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 at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend 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 at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 JSON Patch Non-Atomic Application Destroys Data Before Validation | Advisories | VulnCheck

https://www.vulncheck.com/advisories/cjson-json-patch-non-atomic-application-destroys-data-before-validation
generic

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

https://github.com/DaveGamble/cJSON/blob/v1.7.19/cJSON_Utils.c#L887-L948
generic🟡 PoC Available

33 Vulnerabilities in cJSON | Joshua Rogers' Scribbles

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

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-67217?
CVE-2026-67217 is a medium vulnerability published on July 29, 2026. cJSON through 1.7.19 applies RFC 6902 JSON Patch operations non-atomically in applypatch() in cJSONUtils.c. For a replace operation that is missing its value member, or a move operation whose destination path cannot be resolved, the existing target member is detached and deleted before the…
When was CVE-2026-67217 disclosed?
CVE-2026-67217 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-67217 actively exploited?
CVE-2026-67217 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67217?
CVE-2026-67217 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-67217?
A fix for CVE-2026-67217 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-67217 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-67217

Explore →

Is Your Infrastructure Affected by CVE-2026-67217?

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

Book a Demo →Browse All CVEs