dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-1615

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-09
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The jsonpath library versions before 1.3.0 use the unsafe static-eval module to evaluate user-supplied JSON Path expressions. An attacker can inject malicious JavaScript code through crafted JSON Path expressions, achieving Remote Code Execution in Node.js environments or Cross-site Scripting in browser contexts.

MitigationUpgrade jsonpath to version 1.3.0 or later, which uses a safe evaluation method instead of static-eval.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify jsonpath dependency
    Check your project's package.json, package-lock.json, or node_modules for the jsonpath package. Run 'npm list jsonpath' or 'npm ls jsonpath' to see if it is installed.
    Affected if jsonpath is listed as a dependency in your project
  2. Determine installed jsonpath version
    Run 'npm list jsonpath --depth=0' or check the version field in node_modules/jsonpath/package.json to see the exact version number.
    Affected if The version is lower than 1.3.0 (e.g., 1.2.x, 1.1.x, 1.0.x, etc.)
  3. Identify code paths using affected methods
    Search your codebase for calls to jsonpath.query(), jsonpath.nodes(), jsonpath.paths(), jsonpath.value(), jsonpath.parent(), or jsonpath.apply(). Review where the input arguments originate.
    Affected if Any of these methods are called with user-supplied or untrusted input without prior validation
  4. Check for static-eval usage
    Examine the node_modules/jsonpath/ directory. Look for references to 'static-eval' in the package.json dependencies or in the source code files.
    Affected if static-eval is listed as a dependency or imported in the jsonpath library code

Your environment is affected if jsonpath version is below 1.3.0 AND your code passes untrusted input to the .query, .nodes, .paths, .value, .parent, or .apply methods.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade jsonpath to version 1.3.0 or later, which uses a safe evaluation method instead of static-eval.

Recommended fix High confidence

jsonpath version 1.3.0 or later

  1. Run 'npm list jsonpath' to verify current installed version
  2. Run 'npm install [email protected]' or 'npm update jsonpath' to upgrade to the fixed version
  3. Verify the upgrade was successful by running 'npm list jsonpath'
  4. If using a package-lock.json, run 'npm install' to ensure lockfile is updated
  5. Test that your JSON Path queries still function correctly after the upgrade
Caveat Review the changelog between your current version and 1.3.0 for any breaking changes in the API

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1615 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1615 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data