CVE-2026-67217

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreHIGH 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%CVSS: 5.3Exploit: 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 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.3(high)
EG Risk
55(Attend)
EG Risk 55/100SSVC: Attend

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%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
22%
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 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 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 16× in last 7d / 80× 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.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-25 08:41 UTCEG score recompute
  3. 2026-08-25 08:41 UTCGHSA enrichment
  4. 2026-08-24 06:29 UTCGHSA enrichment
  5. 2026-08-23 04:18 UTCEG score recompute
  6. 2026-08-23 04:18 UTCGHSA enrichment
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-22 02:07 UTCEG score recompute
  9. 2026-08-22 02:06 UTCGHSA enrichment
  10. 2026-08-21 23:49 UTCEPSS rescore
  11. 2026-08-20 23:54 UTCEG score recompute
  12. 2026-08-20 23:54 UTCGHSA enrichment
  13. 2026-08-20 22:56 UTCEPSS rescore
  14. 2026-08-19 21:44 UTCEG score recompute
  15. 2026-08-19 21:44 UTCGHSA enrichment
  16. 2026-08-19 17:04 UTCEPSS rescore
  17. 2026-08-18 19:33 UTCEG score recompute
  18. 2026-08-18 19:33 UTCGHSA enrichment
  19. 2026-08-18 13:48 UTCEPSS rescore
  20. 2026-08-17 17:22 UTCEG score recompute
  21. 2026-08-17 17:22 UTCGHSA enrichment
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-16 15:10 UTCEG score recompute
  24. 2026-08-16 15:10 UTCGHSA enrichment
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 55 more
  1. 2026-08-15 13:00 UTCEG score recompute
  2. 2026-08-15 13:00 UTCGHSA enrichment
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 10:49 UTCEG score recompute
  5. 2026-08-14 10:49 UTCGHSA enrichment
  6. 2026-08-13 22:00 UTCEPSS rescore
  7. 2026-08-13 08:39 UTCEG score recompute
  8. 2026-08-13 08:39 UTCGHSA enrichment
  9. 2026-08-12 13:51 UTCEPSS rescore
  10. 2026-08-12 06:28 UTCEG score recompute
  11. 2026-08-12 06:28 UTCGHSA enrichment
  12. 2026-08-11 04:17 UTCEG score recompute
  13. 2026-08-11 04:17 UTCGHSA enrichment
  14. 2026-08-11 00:00 UTCEPSS rescore
  15. 2026-08-10 02:06 UTCEG score recompute
  16. 2026-08-10 02:06 UTCGHSA enrichment
  17. 2026-08-09 13:47 UTCEPSS rescore
  18. 2026-08-08 23:56 UTCEG score recompute
  19. 2026-08-08 23:56 UTCGHSA enrichment
  20. 2026-08-08 16:37 UTCEPSS rescore
  21. 2026-08-07 21:45 UTCEG score recompute
  22. 2026-08-07 21:45 UTCGHSA enrichment
  23. 2026-08-06 19:35 UTCEG score recompute
  24. 2026-08-06 19:35 UTCGHSA enrichment
  25. 2026-08-06 13:47 UTCEPSS rescore
  26. 2026-08-05 19:17 UTCEPSS rescore
  27. 2026-08-05 19:17 UTCEPSS rescore
  28. 2026-08-05 17:24 UTCGHSA enrichment
  29. 2026-08-04 15:14 UTCEG score recompute
  30. 2026-08-04 15:14 UTCGHSA enrichment
  31. 2026-08-04 15:10 UTCEPSS rescore
  32. 2026-08-04 10:39 UTCEPSS rescore
  33. 2026-08-04 03:55 UTCEG score recompute
  34. 2026-08-04 03:55 UTCGHSA enrichment
  35. 2026-08-03 10:36 UTCEPSS rescore
  36. 2026-08-03 01:45 UTCEG score recompute
  37. 2026-08-03 01:45 UTCGHSA enrichment
  38. 2026-08-02 02:27 UTCEPSS rescore
  39. 2026-08-01 23:34 UTCEG score recompute
  40. 2026-08-01 23:34 UTCGHSA enrichment
  41. 2026-08-01 04:16 UTCEPSS rescore
  42. 2026-07-31 21:23 UTCGHSA enrichment
  43. 2026-07-30 19:09 UTCGHSA enrichment
  44. 2026-07-30 18:45 UTCEG score recompute
  45. 2026-07-30 18:45 UTCGHSA enrichment
  46. 2026-07-30 16:28 UTCEPSS rescore
  47. 2026-07-29 16:25 UTCEG score recompute
  48. 2026-07-29 16:25 UTCGHSA enrichment
  49. 2026-07-29 16:07 UTCEG score recompute
  50. 2026-07-29 16:07 UTCGHSA enrichment
  51. 2026-07-29 15:33 UTCEG score recompute
  52. 2026-07-29 15:33 UTCGHSA enrichment
  53. 2026-07-29 14:19 UTCEG score recompute
  54. 2026-07-29 13:58 UTCEG score recompute
  55. 2026-07-29 13:57 UTCMITRE cvelistV5first tracked

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 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-67217 actively exploited?
CVE-2026-67217 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 78.2% of all scored CVEs.
What is the CVSS score of CVE-2026-67217?
CVE-2026-67217 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-67217?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67217, 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-67217

Explore →

Is Your Infrastructure Affected by CVE-2026-67217?

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