LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1615: Versions of the package jsonpath before 1.3.0 are vulnerable to Arbitrary Code Injection via unsafe evaluat...

Versions of the package jsonpath before 1.3.0 are vulnerable to Arbitrary Code Injection via unsafe evaluation of user-supplied JSON Path expressions. The library relies on the static-eval module to process JSON Path input, which is not designed to handle untrusted data safely. An attacker can exploit this vulnerability by supplying a malicious JSON Path expression that, when evaluated, executes arbitrary JavaScript code, leading to Remote Code Execution in Node.js environments or Cross-site Scripting (XSS) in browser contexts. This affects all methods that evaluate JSON Paths against objects, including .query, .nodes, .paths, .value, .parent, and .apply.

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

The jsonpath library can execute attacker-supplied JavaScript when an application evaluates an untrusted JSON Path. A successful attack could compromise a Node.js service or run script in a user’s browser. Risk depends on whether external input reaches the library’s path-evaluation methods.

Executive priority

Treat internet-facing or multi-tenant systems that evaluate externally influenced JSON Paths as an immediate priority. Upgrade rapidly and restrict that input path pending deployment. Systems using the package only with fixed, trusted expressions remain affected by version but have lower practical exposure; validate rather than assuming safety.

Technical view

jsonpath versions before 1.3.0 unsafely evaluate JSON Path expressions through static-eval. The issue affects query, nodes, paths, value, parent, and apply. Crafted expressions may cause arbitrary JavaScript execution, producing remote code execution in Node.js or cross-site scripting in browsers. It is classified as CWE-94 with CVSS 3.1 score 9.8.

Likely exposure

Exposure includes applications using jsonpath before 1.3.0, directly or transitively, including the org.webjars.npm:jsonpath packaging. Practical exposure is highest where users, API clients, uploaded content, or other untrusted sources can influence JSON Path expressions evaluated by affected methods.

Exploitation context

The supplied sources describe network-reachable, unauthenticated exploitation with low complexity and no user interaction. They do not establish active exploitation, and the CVE is not identified as CISA KEV in the bundle. Public technical references and a corrective commit exist, so prompt remediation remains warranted.

Researcher notes

The central condition is attacker influence over the evaluated path expression, not merely the JSON object being searched. Review wrappers and indirect call sites for all six named methods. The bundle supports arbitrary code execution impact and a 1.3.0 boundary, but provides no evidence here of observed exploitation or confirmed compromise indicators.

Mitigation direction

  • Upgrade jsonpath to version 1.3.0 or later after compatibility testing.
  • Update affected org.webjars.npm:jsonpath dependencies using applicable vendor guidance.
  • Prevent untrusted input from controlling JSON Path expressions until upgrades are complete.
  • Apply relevant Red Hat errata where affected Red Hat products supply the component.

Validation and detection

  • Inventory direct and transitive jsonpath and org.webjars.npm:jsonpath dependencies.
  • Confirm deployed artifacts contain jsonpath 1.3.0 or later.
  • Trace whether external input reaches any affected JSON Path evaluation method.
  • Review application telemetry for unexpected failures or behavior around JSON Path processing.
  • Retest affected workflows after upgrading, including server and browser usage where applicable.
Prepared
Confidence
high
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1615 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

3CVSS vectors
5Timeline events
2ADP providers
12Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

3 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P3.95.9snyk
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9redhat-SADP
9.2CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P——snyk

Vulnerability scoring details

Base CVSS 4.0 score

9.2Critical
CVSS 4.0 vector shape for CVE-2026-1615Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPjsonpath: jsonpath: Arbitrary Code Execution via unsafe JSON Path expression evaluation
other:Red Hat severity ratingcvssV3_1
  • 2026-02-09T11:10:57.572Z: Reported to Red Hat.
  • 2026-02-09T05:00:09.050Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/ajsonpath0Listed
n/aorg.webjars.npm:jsonpath0Listed
Weakness

CWE details

CWE-94

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs