CVE-2022-46175
Prototype Pollution in JSON5 via Parse Method
Reported by github_m · Published December 24, 2022
json5 is fixed in 2.2.2 and 1.0.2 (npm)
JSON5 is an extension to the popular JSON file format that aims to be easier to write and maintain by hand (e.g. for config files). The `parse` method of the JSON5 library before and including versions 1.0.1 and 2.2.1 does not restrict parsing of keys named `__proto__`, allowing specially crafted strings to pollute the prototype of the resulting object. This vulnerability pollutes the prototype of the object returned by `JSON5.parse` and not the global Object prototype, which is the commonly understood definition of Prototype Pollution. However, polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations. This vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned from `JSON5.parse`. The actual impact will depend on how applications utilize the returned object and how they filter unwanted keys, but could include denial of service, cross-site scripting, elevation of privilege, and in extreme cases, remote code execution. `JSON5.parse` should restrict parsing of `__proto__` keys when parsing JSON strings to objects. As a point of reference, the `JSON.parse` method included in JavaScript ignores `__proto__` keys. Simply changing `JSON5.parse` to `JSON.parse` in the examples above mitigates this vulnerability. This vulnerability is patched in json5 versions 1.0.2, 2.2.2, and later.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| json5 | npm | 2.2.2, 1.0.2 |
| json5 | json5 | 2.2.2, 1.0.2 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| json5 | json5 | < 2.2.2 |
| json5 | json5 | |
| npm | json5 | 0, 2.0.0 |
| wolfi | py3-json5 | * |
| json5 | json5 | 0 |
| chainguard | py3-json5 | * |
Timeline
- Dec 24, 2022 CVE Published
- Dec 24, 2022 EPSS Score (30 in total, the first dated here)
- Nov 21, 2024 CVE Updated
- Mar 9, 2026 Security Advisory (59 in total, the first dated here)
- Jun 11, 2026 Coalition ESS Score
- Jul 2, 2026 Distribution Patch (56 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2022-46175
vulnetix vdb fixes CVE-2022-46175
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2022-46175/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart