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

CVE-2026-1615 affects the jsonpath package before 1.3.0. If an application lets users supply JSONPath expressions, a malicious expression may run JavaScript. In Node.js this can become remote code execution; in browser use it may become XSS. The severity is critical because exploitation needs no authentication or user interaction in the stated CVSS model.

Executive priority

Treat as urgent for any application that accepts user-controlled JSONPath input. Critical impact, network exploitability, and no-auth conditions justify rapid inventory and patching. Business urgency is lower only where jsonpath is absent or used solely with trusted static expressions.

Technical view

jsonpath evaluates JSONPath input using static-eval, which the source describes as unsafe for untrusted data. The issue affects methods that evaluate paths, including query, nodes, paths, value, parent, and apply. Affected packages include npm jsonpath and org.webjars.npm:jsonpath before 1.3.0. CWE-94 and CVSS 9.8 indicate code injection impact.

Likely exposure

Highest exposure is in services, APIs, rules engines, dashboards, or browser features that accept JSONPath expressions from users, tenants, webhooks, configuration, or stored records. Internal-only use with trusted, fixed expressions is lower risk but still should be upgraded.

Exploitation context

The bundle does not show CISA KEV listing or confirmed active exploitation. It describes attacker-supplied JSONPath expressions causing arbitrary JavaScript execution, with proof-of-concept maturity indicated in the CVSS vector. Do not assume internet-wide exploitation without additional evidence.

Researcher notes

Focus validation on data-flow, not just package presence. The dangerous condition is evaluation of untrusted JSONPath input through jsonpath methods. The source bundle supports a fixed-before boundary of 1.3.0, but does not provide evidence of active exploitation in the wild.

Mitigation direction

  • Upgrade jsonpath and WebJars jsonpath consumers to version 1.3.0 or later.
  • Block untrusted users from supplying JSONPath expressions until upgraded.
  • Review vendor advisories from Snyk and Red Hat for package-specific guidance.
  • Redeploy applications after dependency updates and verify lockfiles changed.
  • Prioritize externally reachable services and multi-tenant processing paths first.

Validation and detection

  • Inventory npm and Maven/WebJars dependencies for jsonpath versions below 1.3.0.
  • Search application code for query, nodes, paths, value, parent, and apply usage.
  • Identify whether JSONPath expressions can originate from users, APIs, webhooks, or stored content.
  • Run dependency scanning against production lockfiles and container images.
  • Confirm patched builds no longer include vulnerable transitive jsonpath versions.
Prepared
Confidence
high
Sources
12

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
11Source 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.