Skip to content

Comments

Update dependency jsonpath to v1.2.1 [SECURITY] - autoclosed#215

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-jsonpath-vulnerability
Closed

Update dependency jsonpath to v1.2.1 [SECURITY] - autoclosed#215
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-jsonpath-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 5, 2026

This PR contains the following updates:

Package Change Age Confidence
jsonpath 1.1.11.2.1 age confidence

GitHub Vulnerability Alerts

CVE-2026-1615

Impact

Arbitrary Code Injection (Remote Code Execution & XSS):

A critical security vulnerability affects all versions of the jsonpath package. The library relies on the static-eval module to evaluate JSON Path expressions but fails to properly sanitize or sandbox the input.

This allows an attacker to inject arbitrary JavaScript code into the JSON Path expression. When the library evaluates this expression, the malicious code is executed.

  • Node.js Environments: This leads to Remote Code Execution (RCE), allowing an attacker to compromise the server.
  • Browser Environments: This leads to Cross-Site Scripting (XSS), allowing an attacker to hijack user sessions or exfiltrate data.

Affected Methods:

The vulnerability triggers when untrusted data is passed to any method that evaluates a path, including:

  • jsonpath.query
  • jsonpath.nodes
  • jsonpath.paths
  • jsonpath.value
  • jsonpath.parent
  • jsonpath.apply

Patches

No Patch Available:

Currently, all versions of jsonpath are vulnerable. There is no known patched version of this package that resolves the issue while retaining the current architecture.

Recommendation:

Developers are strongly advised to migrate to a secure alternative (such as jsonpath-plus or similar libraries that do not use eval/static-eval) or strictly validate all JSON Path inputs against a known allowlist.

Workarounds

  • Strict Input Validation: Ensure that no user-supplied data is ever passed directly to jsonpath functions.
  • Sanitization: If user input is unavoidable, implement a strict parser to reject any JSON Path expressions containing executable JavaScript syntax (e.g., parentheses (), script expressions script:, or function calls).

Resources


Release Notes

dchester/jsonpath (jsonpath)

v1.2.1

Compare Source

v1.2.0

Compare Source


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Feb 5, 2026
@renovate renovate bot changed the title Update dependency jsonpath to v1.2.0 [SECURITY] Update dependency jsonpath to v1.2.0 [SECURITY] - autoclosed Feb 5, 2026
@renovate renovate bot closed this Feb 5, 2026
@renovate renovate bot deleted the renovate/npm-jsonpath-vulnerability branch February 5, 2026 20:42
@renovate renovate bot changed the title Update dependency jsonpath to v1.2.0 [SECURITY] - autoclosed Update dependency jsonpath to v1.2.1 [SECURITY] Feb 12, 2026
@renovate renovate bot reopened this Feb 12, 2026
@renovate renovate bot force-pushed the renovate/npm-jsonpath-vulnerability branch 2 times, most recently from 2a493ba to b77e8f3 Compare February 12, 2026 15:32
@sonarqubecloud
Copy link

@renovate renovate bot changed the title Update dependency jsonpath to v1.2.1 [SECURITY] Update dependency jsonpath to v1.2.1 [SECURITY] - autoclosed Feb 12, 2026
@renovate renovate bot closed this Feb 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants