Skip to main content
Public proof of conceptFix available

CVE-2022-46175

A public proof of concept exists; no exploitation attested.

  • Published2022-12-24
  • Fixed in2.2.2 · 1.0.2
  • WeaknessCWE-1321

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2022-12-2404:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-11-03 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-46175?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-46175?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
Json5
BranchAffectedFixed in
2.x≥ 2.0.0, < 2.2.22.2.2
1.0< 1.0.21.0.2
Fedoraproject fedora
BranchAffectedFixed in
37.x= 37no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • @rootio/json5Root:npmall versions · fixed in 0.5.1-root.io.1
  • @rootio/json5Root:npmall versions · fixed in 0.5.1-root.io.2
  • @rootio/json5Root:npmall versions · fixed in 1.0.1-root.io.1
  • @rootio/json5Root:npmall versions · fixed in 2.1.3-root.io.1
  • @rootio/json5Root:npmall versions · fixed in 2.2.1-root.io.1
  • js-jqueryAzure Linux:3all versions · no fixed version listed
  • json5TuxCare:npmfrom 0.4.0-tuxcare.0 · fixed in 0.4.0-tuxcare.1
  • json5TuxCare:npmfrom 0.5.1-tuxcare.0 · fixed in 0.5.1-tuxcare.1

22 more package ranges on OSV.dev

Vendor advisories

  • CVE-2022-46175 Red Hat Product Security30 products fixed · 51 known affected

    json5: Prototype Pollution in JSON5 via Parse Method

    migration-toolkit-virtualization/mtv-ui-rhel8 as a component of Migration Toolkit for Virtualization · openshift-pipelines/pipelines-hub-ui-rhel8 as a component of OpenShift Pipelines · openshift-service-mesh/kiali-rhel8 as a component of OpenShift Service Mesh 2.1 · +48 more

  • RHSA-2025:19094 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: Red Hat OpenShift Dev Spaces 3.24.0 Release.

  • RHSA-2024:4631 Red Hat Product Security3 products fixed

    Red Hat Security Advisory: Red Hat OpenShift Dev Spaces 3.15.0 release

  • RHSA-2023:3742 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.13.0 security and bug fix update

  • RHSA-2023:1428 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Migration Toolkit for Containers (MTC) 1.7.8 security and bug fix update

  • RHSA-2023:1043 Red Hat Product Security3 products fixed

    Red Hat Security Advisory: Red Hat Single Sign-On 7.6.2 security update on RHEL 7

6 more advisories

Full record on NVD

Fix

  1. Update Json5 to 2.2.2 · 1.0.2
  2. Vendor fix Red Hat Product Security RHSA-2025:19094 · 4 productsBefore applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
  3. Vendor fix Red Hat Product Security RHSA-2024:4631 · 3 productsBefore applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
  4. Vendor fix Red Hat Product Security RHSA-2023:3742 · 4 productsThese updated images include numerous enhancements and bug fixes. Space precludes documenting all of these changes in this advisory. Users are directed to the Red Hat OpenShift Data Foundation Release Notes for information on the most significant of these changes: https://access.redhat.com/documen…
  5. Vendor fix Red Hat Product Security RHSA-2023:1428 · 1 productFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

Advisories and patches

Detection

read 2026-11-03 22:42 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
1 repository, unverifiedgiz-berlin/quasar-app-webpack-json5-vulnerability
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2022-12-24
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-9c47-m6qq-7p4h

Frequently asked questions

What is CVE-2022-46175?

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.

Is CVE-2022-46175 actively exploited?

Active exploitation of CVE-2022-46175 has not been confirmed. Its EPSS score was 9.7% on 2026-11-03, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-46175?

CVE-2022-46175 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running json5? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record