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
“—” beside the score: it is equal to NVD's CVSS score.
Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2022-08-18. NVD baseline CVSS 10.0; sources differ by 0.0.
Also known asEUVD-2022-6574 (ENISA EUVD) · GHSA-j3rv-w43q-f9x2 (GitHub Security Advisories)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 10.0
- EG Score
- 10.0CRITICALmedium confidence
- EG Risk
- 76EG Risk 76/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity100% × 45%Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.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
- 74th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.
- EG Severity
- 10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 1.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
August 15, 2022
Last Modified
November 21, 2024
Advisory Details (2)
Auto-updated Nov 1, 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.2Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| npm | react-editable-json-tree @ 2.2.2 (fixes < 2.2.2) | — | ghsa |
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)
| 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 16× in last 7d / 52× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 98 of 227 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 129 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-01 20:55 UTCEG score recompute
- 2026-11-01 20:55 UTCGHSA enrichmentGHSA-j3rv-w43q-f9x2 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-11-01 16:30 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-11-01 08:25 UTCGHSA enrichmentGHSA-j3rv-w43q-f9x2 · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-11-01 08:25 UTCEG score recompute
- 2026-10-31 18:32 UTCEG score recompute
- 2026-10-31 16:29 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-30 16:30 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-30 16:05 UTCEG score recompute
- 2026-10-29 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-29 13:42 UTCEG score recompute
- 2026-10-28 16:28 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-28 11:17 UTCEG score recompute
- 2026-10-27 16:28 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-27 08:20 UTCEG score recompute
- 2026-10-26 16:28 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-25 18:04 UTCEG score recompute
- 2026-10-25 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-25 01:20 UTCEG score recompute
- 2026-10-24 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-23 22:58 UTCEG score recompute
- 2026-10-23 16:28 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-22 20:36 UTCEG score recompute
- 2026-10-22 16:30 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-21 18:10 UTCEG score recompute
Show 73 moreShow fewer
- 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-20 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-20 15:48 UTCEG score recompute
- 2026-10-19 16:28 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-19 13:24 UTCEG score recompute
- 2026-10-18 16:28 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-18 08:31 UTCEG score recompute
- 2026-10-17 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-17 06:10 UTCEG score recompute
- 2026-10-16 16:35 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-16 03:46 UTCEG score recompute
- 2026-10-15 16:28 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-15 00:41 UTCEG score recompute
- 2026-10-14 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-13 21:11 UTCEG score recompute
- 2026-10-13 16:29 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-12 18:21 UTCEG score recompute
- 2026-10-12 16:30 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-11 23:15 UTCEG score recompute
- 2026-10-11 13:44 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-10 19:56 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-09 20:04 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-10-08 16:40 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-10-07 23:45 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-10-06 15:14 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-10-05 17:40 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-10-03 14:23 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-10-02 16:23 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-10-01 19:47 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-30 15:59 UTCEG score recompute
- 2026-09-30 15:00 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-29 15:16 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-27 13:42 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-26 00:22 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-24 14:12 UTCOSV refresh
- 2026-09-24 14:00 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-22 14:45 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-19 15:38 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-17 19:24 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-16 14:05 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
- 2026-09-15 03:07 UTCEPSS rescoreEPSS 1.5% · 71st percentile
- 2026-09-12 14:57 UTCEPSS rescoreEPSS 1.5% · 71st percentile
- 2026-09-11 14:50 UTCEPSS rescoreEPSS 1.5% · 71st percentile
- 2026-09-11 09:33 UTCEPSS rescoreEPSS 1.5% · 71st percentile
- 2026-09-08 21:57 UTCEPSS rescoreEPSS 1.5% · 71st percentile
- 2026-09-07 15:58 UTCEPSS rescoreEPSS 1.5% · 71st percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 1.5% · 71st percentile
- 2026-09-05 15:25 UTCEPSS rescoreEPSS 1.5% · 71st percentile
- 2026-09-05 06:44 UTCOSV refresh
- 2026-09-04 13:57 UTCEPSS rescoreEPSS 1.5% · 71st percentile
- 2026-09-04 05:04 UTCEPSS rescoreEPSS 1.5% · 71st percentile
- 2026-09-02 14:09 UTCEPSS rescoreEPSS 1.5% · 71st percentile
- 2026-09-01 13:51 UTCEPSS rescoreEPSS 1.5% · 71st percentile
- 2026-08-30 19:14 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-30 01:19 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-28 21:38 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-27 14:22 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-26 14:43 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-25 13:46 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-24 14:13 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-23 00:17 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-21 23:46 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-20 22:52 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-19 17:01 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-18 17:28 UTCOSV refresh
- 2026-08-18 13:45 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-17 13:44 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-16 14:53 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-16 02:11 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-15 01:27 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-13 21:58 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-12 13:48 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-11 13:39 UTCEPSS rescoreEPSS 1.2% · 66th percentile
Related CVEs(same CWE)
Same CWE
10 shownCWE-95
- CVE-2022-38193NVD 6.1EG 9.6CRITICAL
- CVE-2022-31181EG 9.8EPSS p94CRITICAL
- 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 p100CRITICAL
- CVE-2023-0089EG 8.8HIGH
- CVE-2023-0090EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2022-36010?
When was the CVE record for CVE-2022-36010 published?
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.