dbcve.org
JsonpathApplication · Dchester

CVE-2025-61140

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
The value function in jsonpath 1.1.1 lib/index.js is vulnerable to Prototype Pollution.

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 · moderate confidence

The value function in jsonpath library version 1.1.1 (lib/index.js) is vulnerable to Prototype Pollution, allowing an attacker to manipulate Object.prototype by injecting properties through user-controlled JSONPath queries. This can lead to denial of service, code injection, or privilege escalation in applications using this library.

MitigationUpdate to a patched version of jsonpath if available. Otherwise, implement strict input validation and sanitization on all JSONPath query parameters to prevent prototype manipulation, or sanitize/escape any '$' characters in user input before passing to the library.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JsonpathApplication
Affected:= 1.1.1

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. Check installed jsonpath version
    Run 'npm list jsonpath' or check your package.json/package-lock.json for the jsonpath dependency version
    Affected if The version listed is exactly 1.1.1
  2. Verify jsonpath is in use
    Search your codebase for 'require("jsonpath")' or 'import ... from "jsonpath"' statements to confirm the library is imported
    Affected if Your application imports or requires the jsonpath library
  3. Identify jsonpath function calls in your code
    Search for usages of jsonpath methods such as query, value, paths, nodes, or slice in your source code
    Affected if Your code calls jsonpath methods like query() or value() with dynamic data
  4. Check if external input reaches jsonpath
    Trace data flow from HTTP request parameters, user inputs, or API payloads to jsonpath function calls. Look for code paths where req.body, req.query, or similar user-controlled data is passed to jsonpath
    Affected if Unsanitized user input or external data is passed directly to jsonpath functions without validation
  5. Inspect for prototype pollution payloads
    Review any dynamic property access patterns in your jsonpath queries that might include __proto__, constructor, or prototype as keys
    Affected if Your jsonpath queries accept or construct keys from untrusted input that could include __proto__ or constructor.prototype

You are affected if you have jsonpath version 1.1.1 installed AND your application passes unsanitized external input to jsonpath query functions, allowing an attacker to inject __proto__ or constructor.prototype properties.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of jsonpath if available. Otherwise, implement strict input validation and sanitization on all JSONPath query parameters to prevent prototype manipulation, or sanitize/escape any '$' characters in user input before passing to the library.

Recommended fix Moderate confidence

jsonpath version 2.x or latest stable release

  1. 1. Identify all projects and dependencies that depend on jsonpath version 1.1.1
  2. 2. Run 'npm list jsonpath' or 'npm audit' to confirm the vulnerable version is in use
  3. 3. Update jsonpath to the latest available version using: npm install jsonpath@latest
  4. 4. Alternatively, update in package.json by changing the version to ^2.0.0 or latest, then run npm install
  5. 5. Re-run tests to verify functionality is preserved
  6. 6. Re-scan with npm audit to confirm the vulnerability is resolved
Caveat Potential breaking changes may exist between 1.x and 2.x; review the library's changelog and run test suites

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

Fix this in Jsonpath Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61140 — 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-2025-61140 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