CVE-2022-46175

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 44.1%, top 2% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 9%CVSS: 7.1Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
94.8%
KEV
Not listed

Published

December 24, 2022

Last Modified

November 21, 2024

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunode-json5 (2.2.0+dfsg-1ubuntu0.1~esm1) @ jammy2026-05-25ubuntu
redhatdevspaces/code-rhel9:3.24-17606765692025-10-23redhat
redhatdevspaces/dashboard-rhel8:3.15-62024-07-18redhat
redhatodf4/mcg-core-rhel9:v4.13.0-412023-06-21redhat
redhatrhmtc/openshift-migration-ui-rhel8:v1.7.8-52023-03-23redhat
redhatrh-sso-7/sso76-openshift-rhel8:7.6-202023-03-01redhat
redhatjson52023-03-01redhat
redhatrh-sso7-keycloak-0:18.0.6-1.redhat_00001.1.el7sso2023-03-01redhat
redhatrh-sso7-keycloak-0:18.0.6-1.redhat_00001.1.el9sso2023-03-01redhat
redhatrh-sso7-keycloak-0:18.0.6-1.redhat_00001.1.el8sso2023-03-01redhat
redhatmta/mta-ui-rhel8:6.0.1-102023-02-28redhat
redhatopenshift-logging/logging-view-plugin-rhel8:v5.6.1-82023-02-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
json51.0.2

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 40× 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-07-11 08:25 UTCEPSS rescore
  2. 2026-07-11 08:25 UTCEPSS rescore
  3. 2026-07-09 19:08 UTCEPSS rescore
  4. 2026-07-08 15:12 UTCEPSS rescore
  5. 2026-07-07 13:44 UTCEPSS rescore
  6. 2026-07-06 16:25 UTCEPSS rescore
  7. 2026-07-05 02:28 UTCEPSS rescore
  8. 2026-07-04 06:29 UTCEPSS rescore
  9. 2026-07-02 16:58 UTCEPSS rescore
  10. 2026-07-01 15:04 UTCEPSS rescore
  11. 2026-06-30 23:20 UTCEPSS rescore
  12. 2026-06-30 23:20 UTCEPSS rescore
  13. 2026-06-29 14:04 UTCEPSS rescore
  14. 2026-06-29 14:04 UTCEPSS rescore
  15. 2026-06-28 10:19 UTCOSV refresh
  16. 2026-06-28 04:54 UTCEPSS rescore
  17. 2026-06-28 04:54 UTCEPSS rescore
  18. 2026-06-27 03:07 UTCEPSS rescore
  19. 2026-06-27 03:07 UTCEPSS rescore
  20. 2026-06-25 13:48 UTCEPSS rescore
  21. 2026-06-25 13:48 UTCEPSS rescore
  22. 2026-06-24 14:03 UTCEPSS rescore
  23. 2026-06-23 21:31 UTCEPSS rescore
  24. 2026-06-23 21:31 UTCEPSS rescore
  25. 2026-06-22 14:24 UTCEPSS rescore
Show 47 more
  1. 2026-06-21 14:55 UTCEPSS rescore
  2. 2026-06-21 14:55 UTCEPSS rescore
  3. 2026-06-21 01:58 UTCEPSS rescore
  4. 2026-06-21 01:58 UTCEPSS rescore
  5. 2026-06-19 19:24 UTCEPSS rescore
  6. 2026-06-19 19:24 UTCEPSS rescore
  7. 2026-06-18 17:51 UTCEPSS rescore
  8. 2026-06-18 17:51 UTCEPSS rescore
  9. 2026-06-17 17:51 UTCEPSS rescore
  10. 2026-06-17 17:51 UTCEPSS rescore
  11. 2026-06-16 17:51 UTCEPSS rescore
  12. 2026-06-15 17:46 UTCEPSS rescore
  13. 2026-06-13 22:59 UTCEPSS rescore
  14. 2026-06-12 23:10 UTCEPSS rescore
  15. 2026-06-12 23:10 UTCEPSS rescore
  16. 2026-06-11 13:58 UTCEPSS rescore
  17. 2026-06-11 13:58 UTCEPSS rescore
  18. 2026-06-10 22:17 UTCEPSS rescore
  19. 2026-06-10 20:47 UTCOSV refresh
  20. 2026-06-10 13:21 UTCEPSS rescore
  21. 2026-06-10 13:21 UTCEPSS rescore
  22. 2026-06-08 14:15 UTCEPSS rescore
  23. 2026-06-06 13:46 UTCEPSS rescore
  24. 2026-06-06 13:46 UTCEPSS rescore
  25. 2026-06-06 13:46 UTCEPSS rescore
  26. 2026-06-05 22:46 UTCEPSS rescore
  27. 2026-06-05 22:46 UTCEPSS rescore
  28. 2026-06-05 06:09 UTCEPSS rescore
  29. 2026-06-05 06:09 UTCEPSS rescore
  30. 2026-06-04 13:11 UTCEPSS rescore
  31. 2026-06-02 20:12 UTCEPSS rescore
  32. 2026-06-02 20:11 UTCEPSS rescore
  33. 2026-05-31 22:29 UTCEPSS rescore
  34. 2026-05-31 22:29 UTCEPSS rescore
  35. 2026-05-31 00:15 UTCEPSS rescore
  36. 2026-05-31 00:15 UTCEPSS rescore
  37. 2026-05-29 13:43 UTCEPSS rescore
  38. 2026-05-28 13:43 UTCEPSS rescore
  39. 2026-05-28 13:43 UTCEPSS rescore
  40. 2026-05-26 13:43 UTCEPSS rescore
  41. 2026-05-26 13:43 UTCEPSS rescore
  42. 2026-05-26 13:43 UTCEPSS rescore
  43. 2026-05-26 07:17 UTCEPSS rescore
  44. 2026-05-26 07:17 UTCEPSS rescore
  45. 2026-05-26 07:17 UTCEPSS rescore
  46. 2026-05-25 09:49 UTCEG score recompute
  47. 2026-05-25 09:49 UTCVendor advisory

Frequently asked(5)

What is CVE-2022-46175?
CVE-2022-46175 is a high vulnerability published on December 24, 2022. 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…
When was CVE-2022-46175 disclosed?
CVE-2022-46175 was first published in the National Vulnerability Database on December 24, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-46175 actively exploited?
CVE-2022-46175 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 94.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-46175?
CVE-2022-46175 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2022-46175?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-46175, 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-2022-46175

Explore →

Is Your Infrastructure Affected by CVE-2022-46175?

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