DaveGamble cJSON up to 1.7.19 JSON Patch cJSON_Utils.c apply_patch dynamically-managed code resources

Summaryinfo

A vulnerability described as problematic has been identified in DaveGamble cJSON up to 1.7.19. This affects the function apply_patch of the file cJSON_Utils.c of the component JSON Patch. Executing a manipulation can lead to dynamically-managed code resources. This vulnerability is tracked as CVE-2026-67217. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability was found in DaveGamble cJSON up to 1.7.19. It has been declared as problematic. This vulnerability affects the function apply_patch of the file cJSON_Utils.c of the component JSON Patch. The manipulation with an unknown input leads to a dynamically-managed code resources vulnerability. The CWE definition for the vulnerability is CWE-913. The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements. As an impact it is known to affect integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at joshua.hu. This vulnerability was named CVE-2026-67217 since 07/28/2026. The exploitation appears to be easy. The attack can be initiated remotely. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 07/29/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• DaveGamble

Name

• cJSON

Version

• 1.7.0
• 1.7.1
• 1.7.2
• 1.7.3
• 1.7.4
• 1.7.5
• 1.7.6
• 1.7.7
• 1.7.8
• 1.7.9
• 1.7.10
• 1.7.11
• 1.7.12
• 1.7.13
• 1.7.14
• 1.7.15
• 1.7.16
• 1.7.17
• 1.7.18
• 1.7.19

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion