CyberSecBulletin
CVE-2026-1615NVD status: Deferred

jsonpath: Improper Control of Generation of Code

Published Updated By the CyberSecBulletin desk

CVE-2026-1615 is a critical-severity improper control of generation of code vulnerability in jsonpath, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 1.3.0 as the first without the flaw, so updating jsonpath to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.15% chance of exploitation within 30 days, higher than 67% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update jsonpath to 1.3.0 or a later version.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Jsonpathjsonpathbefore 1.3.01.3.0
Org.webjars.npm:jsonpathorg.webjars.npm:jsonpathall versionsNot stated
Red HatRed Hat Ansible Automation Platform 2.5Not specified in the recordNot stated
Red HatRed Hat Ansible Automation Platform 2.6Not specified in the recordNot stated
Red HatRed Hat Developer Hub 1.9Not specified in the recordNot stated
Red HatMigration Toolkit for VirtualizationNot specified in the recordNot stated
Red HatOpenShift PipelinesNot specified in the recordNot stated
Red HatRed Hat Ansible Automation Platform 2Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux AI (RHEL AI) 3Not specified in the recordNot stated
Red HatRed Hat Fuse 7Not specified in the recordNot stated
Red HatRed Hat OpenShift AI (RHOAI)Not specified in the recordNot stated
Red HatRed Hat Quay 3Not specified in the recordNot stated
Red HatSelf-service automation portal 2Not specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (snyk.io).

Scoring systemScoreSeverityScored by
CVSS 4.08.2HighCNA (snyk.io)
CVSS 3.19.8CriticalCNA (snyk.io)
CVSS 3.19.8CriticalCNA

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Control of Generation of Code

The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

How developers prevent this class of flaw

  • Refactor your program so that you do not have to dynamically generate code.
  • Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
  • Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.

More Improper Control of Generation of Code vulnerabilities (CWE-94)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Improper Control of Generation of Code vulnerabilities

Spotted an error? Tell us.