Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 10.0amended

React Editable Json Tree vulnerable to arbitrary code execution via function parsing

CVE-2022-36010GHSA-j3rv-w43q-f9x2

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (react-editable-json-tree 2.2.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
10.0 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
  • CVE-2022-36010: 1.53% estimated exploitation activity in the next 30 days; percentile 74.78 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact Our library allows strings to be parsed as functions and stored as a specialized component, JsonFunctionValue. To do this, Javascript's eval function was used to execute strings that begin with "function" as Javascript. This was an oversight that unfortunately allows 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. Patches We have decided on a two-pronged approach to patching this vulnerability: 1. Create a patch update that adds a workaround which is not enabled by default to preserve backwards-compatibility 2. On the next major update, we will enable this workaround by default The…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-j3rv-w43q-f9x2

  2. Revision 1 · created ·

    Published from osv record GHSA-j3rv-w43q-f9x2

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-36010

Advisory: React Editable Json Tree vulnerable to arbitrary code execution via function parsing
IDs: CVE-2022-36010, GHSA-j3rv-w43q-f9x2
Record: https://patchnext.com/advisories/cve-2022-36010 (revision 2, source checked 26 Oct 2026, 12:17 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 10.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: react-editable-json-tree 2.2.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm react-editable-json-tree: affected < 2.2.2; fixed in 2.2.2

## Suggested inspection (read-only)
- `npm ls react-editable-json-tree --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on react-editable-json-tree.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-j3rv-w43q-f9x2 (OSV record GHSA-j3rv-w43q-f9x2 lists affected ranges: npm react-editable-json-tree >=0 <2.2.2 (fixed))
- Verified: https://github.com/advisories/GHSA-j3rv-w43q-f9x2 (GitHub-reviewed advisory GHSA-j3rv-w43q-f9x2 lists affected ranges: npm react-editable-json-tree >=0 <2.2.2)

Commands are suggestions: review each one before running it.

Loading voting…