{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67217 exists.","fix":"No fix has been published for CVE-2026-67217 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-67217 is a medium-severity vulnerability in DaveGamble cJSON, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-67217 and fix it if it is affected.\n\nWhat it is: CVE-2026-67217 is a medium-severity vulnerability in DaveGamble cJSON, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67217 exists.\n\nAffected product: DaveGamble cJSON. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-67217/ (Markdown: https://insights.sbomify.com/CVE-2026-67217/index.md)","id":"CVE-2026-67217","markdown":"https://insights.sbomify.com/CVE-2026-67217/index.md","name":"CVE-2026-67217","record":{"aliases":["DEBIAN-CVE-2026-67217","GHSA-pr46-97qf-f32c","UBUNTU-CVE-2026-67217"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"JSON parsing library","requires_auth":"none","summary":"Attackers can destroy data in JSON documents by supplying malformed patches that fail validation after mutation, affecting applications using cJSON.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"cjson","vendor":"davegamble"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-696","name":"Incorrect Behavior Order"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"cJSON JSON Patch Non-Atomic Application Destroys Data Before Validation","id":"CVE-2026-67217","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"RabbitMQ: Super-stream HTTP creation skips configure-permission check","id":"CVE-2026-67218"},"packages":[],"prev":{"headline":"cJSON cJSON_Compare Exponential Complexity Denial of Service","id":"CVE-2026-67216"},"products":["cJSON"],"published":"2026-07-29","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2025-57052","kev_date_added":null,"published":"2025-09-03"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-11834","kev_date_added":null,"published":"2019-05-09"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-11835","kev_date_added":null,"published":"2019-05-09"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-10749","kev_date_added":null,"published":"2019-04-29"},{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2018-1000217","kev_date_added":null,"published":"2018-08-20"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2018-1000216","kev_date_added":null,"published":"2018-08-20"},{"cvss_score":8.7,"headline":"cJSON JSON Patch copy/add Uncontrolled Recursion Stack Exhaustion","id":"CVE-2026-67215","kev_date_added":null,"published":"2026-07-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-29","vendors":["DaveGamble"]},"summary":"Attackers can destroy data in JSON documents by supplying malformed patches that fail validation after mutation, affecting applications using cJSON.","url":"https://insights.sbomify.com/CVE-2026-67217/"}