This library allows strings to be parsed as functions and stored as a specialized component, JsonFunctionValue. To do this, Javascript's eval function is used to execute strings that begin with "function" as Javascript. This unfortunately could allow arbitrary code to be executed if it exists as a value within the JSON structure being displayed. Given that this component may often be used to display data from arbitrary, untrusted sources, this is extremely dangerous. One important note is that users who have defined a custom onSubmitValueParser callback prop on the JsonTree component should be *unaffected*. This vulnerability exists in the default onSubmitValueParser prop which calls parse. Prop is added to JsonTree called allowFunctionEvaluation. This prop will be set to true in v2.2.2, which allows upgrade without losing backwards-compatibility. In v2.2.2, we switched from using eval to using Function to construct anonymous functions. This is better than eval for the following reasons: - Arbitrary code should not be able to execute immediately, since the Function constructor explicitly *only creates* anonymous functions - Functions are created without local closures, so they only have access to the global scope If you use: - Version <2.2.2, you must upgrade as soon as possible. - Version ^2.2.2, you must explicitly set JsonTree's allowFunctionEvaluation prop to false to fully mitigate this vulnerability. - Version >=3.0.0, allowFunctionEvaluation is already set to false by default, so no further steps are necessary.
CVE-2022-36010
This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 1.5% (72nd percentile of EPSS-scored CVEs). 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).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 10.0
- EG Score
- 10.0CRITICALmedium confidence
- EG Risk
- 76EG Risk 76/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity100% × 45%Exploitation40% × 40%Automatability100% × 15%CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 1.5%
- EPSS %ILE
- 73rd
- KEV
- Not listed
CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
August 15, 2022
Last Modified
November 21, 2024
Advisory Details (2)
Auto-updated Oct 3, 2026Arbitrary code execution via function parsing · Advisory · oxyno-zeta/react-editable-json-tree · GitHub
https://github.com/oxyno-zeta/react-editable-json-tree/security/advisories/GHSA-j3rv-w43q-f9x22.2.2
Patch available: oxyno-zeta/react-editable-json-tree 2.2.2
https://github.com/oxyno-zeta/react-editable-json-tree/releases/tag/2.2.2Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| react-editable-json-tree | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 23× 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.
Showing the most recent 100 of 183 total refreshes for this CVE.
- 2026-10-09 20:04 UTCEPSS rescore
- 2026-10-08 16:40 UTCEPSS rescore
- 2026-10-07 23:45 UTCEPSS rescore
- 2026-10-06 15:14 UTCEPSS rescore
- 2026-10-05 17:40 UTCEPSS rescore
- 2026-10-03 14:23 UTCEPSS rescore
- 2026-10-02 16:23 UTCEPSS rescore
- 2026-10-01 19:47 UTCEPSS rescore
- 2026-09-30 15:59 UTCEG score recompute
- 2026-09-30 15:00 UTCEPSS rescore
- 2026-09-29 15:16 UTCEPSS rescore
- 2026-09-27 13:42 UTCEPSS rescore
- 2026-09-26 00:22 UTCEPSS rescore
- 2026-09-24 14:12 UTCOSV refresh
- 2026-09-24 14:00 UTCEPSS rescore
- 2026-09-22 14:45 UTCEPSS rescore
- 2026-09-19 15:38 UTCEPSS rescore
- 2026-09-17 19:24 UTCEPSS rescore
- 2026-09-16 14:05 UTCEPSS rescore
- 2026-09-15 03:07 UTCEPSS rescore
- 2026-09-12 14:57 UTCEPSS rescore
- 2026-09-11 14:50 UTCEPSS rescore
- 2026-09-11 09:33 UTCEPSS rescore
- 2026-09-08 21:57 UTCEPSS rescore
- 2026-09-07 15:58 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-09-06 13:45 UTCEPSS rescore
- 2026-09-05 15:25 UTCEPSS rescore
- 2026-09-05 06:44 UTCOSV refresh
- 2026-09-04 13:57 UTCEPSS rescore
- 2026-09-04 05:04 UTCEPSS rescore
- 2026-09-02 14:09 UTCEPSS rescore
- 2026-09-01 13:51 UTCEPSS rescore
- 2026-08-30 19:14 UTCEPSS rescore
- 2026-08-30 01:19 UTCEPSS rescore
- 2026-08-28 21:38 UTCEPSS rescore
- 2026-08-27 14:22 UTCEPSS rescore
- 2026-08-26 14:43 UTCEPSS rescore
- 2026-08-25 13:46 UTCEPSS rescore
- 2026-08-24 14:13 UTCEPSS rescore
- 2026-08-23 00:17 UTCEPSS rescore
- 2026-08-21 23:46 UTCEPSS rescore
- 2026-08-21 23:46 UTCEPSS rescore
- 2026-08-20 22:52 UTCEPSS rescore
- 2026-08-19 17:01 UTCEPSS rescore
- 2026-08-18 17:28 UTCOSV refresh
- 2026-08-18 13:45 UTCEPSS rescore
- 2026-08-17 13:44 UTCEPSS rescore
- 2026-08-16 14:53 UTCEPSS rescore
- 2026-08-16 02:11 UTCEPSS rescore
- 2026-08-15 01:27 UTCEPSS rescore
- 2026-08-13 21:58 UTCEPSS rescore
- 2026-08-13 21:58 UTCEPSS rescore
- 2026-08-12 13:48 UTCEPSS rescore
- 2026-08-11 13:39 UTCEPSS rescore
- 2026-08-10 14:08 UTCEPSS rescore
- 2026-08-09 13:44 UTCEPSS rescore
- 2026-08-08 16:34 UTCEPSS rescore
- 2026-08-07 16:24 UTCEPSS rescore
- 2026-08-06 13:44 UTCEPSS rescore
- 2026-08-05 19:15 UTCEPSS rescore
- 2026-08-05 19:15 UTCEPSS rescore
- 2026-08-04 15:07 UTCEPSS rescore
- 2026-08-04 10:35 UTCEPSS rescore
- 2026-08-03 12:57 UTCOSV refresh
- 2026-08-02 02:24 UTCEPSS rescore
- 2026-08-01 04:13 UTCEPSS rescore
- 2026-07-30 16:25 UTCEPSS rescore
- 2026-07-30 16:25 UTCEPSS rescore
- 2026-07-30 01:28 UTCEPSS rescore
- 2026-07-28 15:33 UTCEPSS rescore
- 2026-07-26 14:52 UTCEPSS rescore
- 2026-07-25 14:15 UTCEPSS rescore
- 2026-07-25 14:15 UTCEPSS rescore
- 2026-07-24 14:15 UTCEPSS rescore
- 2026-07-24 14:15 UTCEPSS rescore
- 2026-07-23 14:16 UTCEPSS rescore
- 2026-07-23 02:12 UTCEG score recompute
- 2026-07-22 22:59 UTCEG score recompute
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-21 15:23 UTCEPSS rescore
- 2026-07-21 15:22 UTCEPSS rescore
- 2026-07-20 17:05 UTCEPSS rescore
- 2026-07-19 14:29 UTCEPSS rescore
- 2026-07-19 02:27 UTCEPSS rescore
- 2026-07-19 02:27 UTCEPSS rescore
- 2026-07-18 10:03 UTCEPSS rescore
- 2026-07-18 10:03 UTCEPSS rescore
- 2026-07-16 22:09 UTCOSV refresh
- 2026-07-16 17:00 UTCEPSS rescore
- 2026-07-15 16:56 UTCEPSS rescore
- 2026-07-15 16:56 UTCEPSS rescore
- 2026-07-15 01:58 UTCEPSS rescore
- 2026-07-15 01:58 UTCEPSS rescore
- 2026-07-13 22:28 UTCEPSS rescore
- 2026-07-13 22:28 UTCEPSS rescore
- 2026-07-12 05:44 UTCEPSS rescore
- 2026-07-12 05:44 UTCEPSS rescore
- 2026-07-11 08:25 UTCEPSS rescore
- 2026-07-09 19:08 UTCEPSS rescore
Related CVEs(same CWE)
Same CWE
10 shownCWE-95
- CVE-2022-38193NVD 6.1EG 9.6CRITICAL
- CVE-2022-36099EG 9.9EPSS p100CRITICAL
- CVE-2022-36100EG 9.9EPSS p99CRITICAL
- CVE-2022-40871EG 9.8EPSS p98CRITICAL
- CVE-2022-41928EG 9.9CRITICAL
- CVE-2022-41931EG 9.9CRITICAL
- CVE-2023-26477EG 10.0EPSS p99CRITICAL
- CVE-2023-0089EG 8.8HIGH
- CVE-2023-0090EG 9.8CRITICAL
- CVE-2023-0888NVD 4.9EG 7.2HIGH
Frequently asked(5)
What is CVE-2022-36010?
When was CVE-2022-36010 disclosed?
Is CVE-2022-36010 actively exploited?
What is the CVSS score of CVE-2022-36010?
How do I remediate CVE-2022-36010?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-36010
Is Your Infrastructure Affected by CVE-2022-36010?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.