CVE-2026-1615

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.0%, top 38% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.2%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
1.2%
EPSS %ILE
66th
KEV
Not listed

Published

February 9, 2026

Last Modified

August 25, 2026

Advisory Details (10)

Auto-updated Oct 6, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: github_commit, redhat.
redhat

2437875 – (CVE-2026-1615) CVE-2026-1615 jsonpath: jsonpath: Arbitrary Code Execution via unsafe JSON Path expression evaluation

https://bugzilla.redhat.com/show_bug.cgi?id=2437875
redhatMentions a patch (unverified)

CVE-2026-1615 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-1615
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:6802
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:6309
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:6308
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:59155
generic🔴 Active Exploitation

Arbitrary Code Injection in jsonpath | CVE-2026-1615 | Snyk

https://security.snyk.io/vuln/SNYK-JS-JSONPATH-13645034
generic🔴 Active Exploitation

Arbitrary Code Injection in org.webjars.npm:jsonpath | CVE-2026-1615 | Snyk

https://security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-15141219
github_commit

commit b61111f07ac1 (dchester/jsonpath)

Fix landed in dchester/jsonpath commit b61111f07ac1 — awaiting tagged release

https://github.com/dchester/jsonpath/commit/b61111f07ac1a8d0f3133b5fc51438ecb76a6c39

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatansible-automation-platform-26/lightspeed-rhel9:17872440792026-08-24redhat
redhatrhdh/rhdh-hub-rhel9:17751406472026-04-07redhat
redhatansible-automation-platform-26/lightspeed-rhel9:17743630402026-04-01redhat
redhatansible-automation-platform-25/lightspeed-rhel8:17744468742026-03-31redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
jsonpath—
  • every version up to 1.3.0: fixed in 1.3.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 223 total refreshes for this CVE.

  1. 2026-10-10 19:59 UTCEPSS rescore
  2. 2026-10-09 20:06 UTCEPSS rescore
  3. 2026-10-08 17:11 UTCEPSS rescore
  4. 2026-10-07 23:47 UTCEPSS rescore
  5. 2026-10-06 15:17 UTCEPSS rescore
  6. 2026-10-05 17:42 UTCEPSS rescore
  7. 2026-10-04 23:21 UTCEPSS rescore
  8. 2026-10-02 13:40 UTCOSV refresh
  9. 2026-10-01 19:49 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-29 15:21 UTCEPSS rescore
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-27 13:47 UTCEPSS rescore
  14. 2026-09-26 15:58 UTCEPSS rescore
  15. 2026-09-18 19:27 UTCEPSS rescore
  16. 2026-09-16 14:07 UTCEPSS rescore
  17. 2026-09-16 05:14 UTCEPSS rescore
  18. 2026-09-13 16:46 UTCEPSS rescore
  19. 2026-09-13 11:54 UTCOSV refresh
  20. 2026-09-12 15:00 UTCEPSS rescore
  21. 2026-09-11 14:52 UTCEPSS rescore
  22. 2026-09-11 09:36 UTCEPSS rescore
  23. 2026-09-10 09:34 UTCEPSS rescore
  24. 2026-09-08 22:00 UTCEPSS rescore
  25. 2026-09-07 16:01 UTCEPSS rescore
Show 75 more
  1. 2026-09-06 13:47 UTCEPSS rescore
  2. 2026-09-04 05:06 UTCEPSS rescore
  3. 2026-09-02 14:11 UTCEPSS rescore
  4. 2026-09-01 13:53 UTCEPSS rescore
  5. 2026-09-01 04:39 UTCEPSS rescore
  6. 2026-08-30 19:17 UTCEPSS rescore
  7. 2026-08-30 01:22 UTCEPSS rescore
  8. 2026-08-28 21:41 UTCEPSS rescore
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-26 14:46 UTCEPSS rescore
  11. 2026-08-25 13:48 UTCEPSS rescore
  12. 2026-08-25 13:26 UTCEG score recompute
  13. 2026-08-25 13:26 UTCVendor advisory
  14. 2026-08-25 13:21 UTCNVD updateCVSS v4 → 8.2
  15. 2026-08-25 12:22 UTCEG score recompute
  16. 2026-08-25 12:22 UTCVendor advisory
  17. 2026-08-23 15:36 UTCEG score recompute
  18. 2026-08-23 15:36 UTCVendor advisory
  19. 2026-08-23 00:19 UTCEPSS rescore
  20. 2026-08-21 23:49 UTCEPSS rescore
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-19 17:03 UTCEPSS rescore
  23. 2026-08-18 13:48 UTCEPSS rescore
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-16 14:56 UTCEPSS rescore
  26. 2026-08-16 02:14 UTCEPSS rescore
  27. 2026-08-15 01:30 UTCEPSS rescore
  28. 2026-08-14 22:47 UTCVendor advisory
  29. 2026-08-14 15:03 UTCVendor advisory
  30. 2026-08-14 10:48 UTCEG score recompute
  31. 2026-08-14 10:48 UTCVendor advisory
  32. 2026-08-13 22:00 UTCEPSS rescore
  33. 2026-08-13 03:07 UTCEG score recompute
  34. 2026-08-13 03:07 UTCVendor advisory
  35. 2026-08-12 13:50 UTCEPSS rescore
  36. 2026-08-11 13:42 UTCEPSS rescore
  37. 2026-08-11 00:00 UTCEPSS rescore
  38. 2026-08-10 09:49 UTCVendor advisory
  39. 2026-08-09 23:56 UTCVendor advisory
  40. 2026-08-09 19:43 UTCVendor advisory
  41. 2026-08-09 15:29 UTCEG score recompute
  42. 2026-08-09 15:29 UTCVendor advisory
  43. 2026-08-09 13:46 UTCEPSS rescore
  44. 2026-08-08 16:37 UTCEPSS rescore
  45. 2026-08-08 06:55 UTCVendor advisory
  46. 2026-08-08 02:41 UTCVendor advisory
  47. 2026-08-07 22:28 UTCEG score recompute
  48. 2026-08-07 22:28 UTCVendor advisory
  49. 2026-08-06 13:46 UTCEPSS rescore
  50. 2026-08-06 08:29 UTCVendor advisory
  51. 2026-08-06 04:10 UTCEG score recompute
  52. 2026-08-06 04:10 UTCVendor advisory
  53. 2026-08-05 19:17 UTCEPSS rescore
  54. 2026-08-04 15:10 UTCEPSS rescore
  55. 2026-08-04 10:38 UTCEPSS rescore
  56. 2026-08-03 10:35 UTCEPSS rescore
  57. 2026-08-03 01:40 UTCVendor advisory
  58. 2026-08-02 21:07 UTCVendor advisory
  59. 2026-08-02 15:38 UTCEG score recompute
  60. 2026-08-02 15:38 UTCVendor advisory
  61. 2026-08-02 02:26 UTCEPSS rescore
  62. 2026-08-01 04:15 UTCEPSS rescore
  63. 2026-07-30 01:30 UTCEPSS rescore
  64. 2026-07-27 14:13 UTCEPSS rescore
  65. 2026-07-26 15:44 UTCEG score recompute
  66. 2026-07-26 15:44 UTCVendor advisory
  67. 2026-07-26 14:54 UTCEPSS rescore
  68. 2026-07-26 14:54 UTCEPSS rescore
  69. 2026-07-25 14:17 UTCEPSS rescore
  70. 2026-07-25 14:17 UTCEPSS rescore
  71. 2026-07-24 14:17 UTCEPSS rescore
  72. 2026-07-23 14:18 UTCEPSS rescore
  73. 2026-07-23 14:18 UTCEPSS rescore
  74. 2026-07-23 03:05 UTCEG score recompute
  75. 2026-07-22 14:08 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-1615?
CVE-2026-1615 is a critical vulnerability published on February 9, 2026. 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…
When was CVE-2026-1615 disclosed?
CVE-2026-1615 was first published on February 9, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-1615 actively exploited?
CVE-2026-1615 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (66th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-1615?
CVE-2026-1615 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-1615?
A fix for CVE-2026-1615 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-1615 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-1615

Explore →

Is Your Infrastructure Affected by CVE-2026-1615?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.