CVE-2026-77415

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9% (59th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-64166 (ENISA EUVD) · GHSA-66mm-25pp-rfff (GitHub Security Advisories)Source: ENISA EUVD

9.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 9.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

JSONata is a JSON query and transformation language. Prior to 1.8.8 and 2.2.1, crafted JSONata expressions could chain several object-integrity weaknesses to execute arbitrary code. The chain could overwrite $clone to mutate objects through evaluateTransformExpression, expose and deconstruct JSONata functions or lambdas through $merge.*, replace proc.arguments.forEach used by applyProcedure, and forge internal lambda state. These primitives allowed an attacker to reach prototype getters, prototype and constructor access, and process.getBuiltinModule with child_process, executing code with the privileges of the host process. This issue is fixed in versions 1.8.8 and 2.2.1.

CVSS
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
73
EG Risk 73/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.9%
EPSS %ILE
59th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 21, 2026

Last Modified

October 12, 2026

Advisory Details (10)

Auto-updated Oct 3, 2026
Patch available. Sources: github_release, github_commit, github_pr.
GitHub release Patch Available

2.2.1 Maintenance Release

Patch available: jsonata-js/jsonata v2.2.1

https://github.com/jsonata-js/jsonata/releases/tag/v2.2.1
GitHub release Patch Available

1.8.8 Security Release

Patch available: jsonata-js/jsonata v1.8.8

https://github.com/jsonata-js/jsonata/releases/tag/v1.8.8
GitHub pull request Patch Available

Prevent object contructor setting internal flags

Patch available: jsonata-js/jsonata v2.2.1 (PR #802 merged 2026-05-19)

https://github.com/jsonata-js/jsonata/pull/802
GitHub pull request Patch Available

Wildcards should not unwrap function objects

Patch available: jsonata-js/jsonata v2.2.1 (PR #800 merged 2026-05-19)

https://github.com/jsonata-js/jsonata/pull/800
GitHub pull request Patch Available

Prevent object prototype pollution

Patch available: jsonata-js/jsonata v2.2.1 (PR #799 merged 2026-05-19)

https://github.com/jsonata-js/jsonata/pull/799
GitHub commit Patch Available

commit f174348c7fa3 (jsonata-js/jsonata)

Patch available: jsonata-js/jsonata v2.2.1 (contains commit f174348c7fa3)

https://github.com/jsonata-js/jsonata/commit/f174348c7fa30f271b63ddedf0767e814004bc4d
GitHub commit Patch Available

commit f09df8416eab (jsonata-js/jsonata)

Patch available: jsonata-js/jsonata v1.8.8 (contains commit f09df8416eab)

https://github.com/jsonata-js/jsonata/commit/f09df8416eab8ff44926fc6527c80fb8701de159
GitHub commit Patch Available

commit 59e25144fc3b (jsonata-js/jsonata)

Patch available: jsonata-js/jsonata v2.2.1 (contains commit 59e25144fc3b)

https://github.com/jsonata-js/jsonata/commit/59e25144fc3b7125f6befd71b8a6e14e1fa610d2
GitHub commit Patch Available

commit 4b217d514376 (jsonata-js/jsonata)

Patch available: jsonata-js/jsonata v1.8.8 (contains commit 4b217d514376)

https://github.com/jsonata-js/jsonata/commit/4b217d514376e30cba278941298d7ba97c4a6c6e
GitHub commit Patch Available

commit 47c0e5854220 (jsonata-js/jsonata)

Patch available: jsonata-js/jsonata v2.2.1 (contains commit 47c0e5854220)

https://github.com/jsonata-js/jsonata/commit/47c0e58542202c705726663166dbee5fcae47d06

Vendor Advisories for CVE-2026-77415(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhdh/red-hat-developer-hub-backstage-plugin-orchestrator-form-widgets:17912507942026-10-06redhat
npmjsonata @ 2.2.1 (fixes >= 2.0.0, < 2.2.1)—ghsa
npmjsonata @ 1.8.8 (fixes < 1.8.8)—ghsa

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
jsonata—
  • 2.0.0 up to 2.2.1: fixed in 2.2.1
  • every version up to 1.8.8: fixed in 1.8.8
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 222 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 122 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 23:19 UTCEchelonGraph re-scored
  2. 2026-11-12 23:19 UTCVendor advisory
  3. 2026-11-12 23:19 UTCGHSA enrichmentGHSA-66mm-25pp-rfff · GitHub severity CRITICAL
  4. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  5. 2026-11-12 00:59 UTCEchelonGraph re-scored
  6. 2026-11-12 00:59 UTCVendor advisory
  7. 2026-11-12 00:59 UTCGHSA enrichmentGHSA-66mm-25pp-rfff · GitHub severity CRITICAL
  8. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  9. 2026-11-11 02:38 UTCEchelonGraph re-scored
  10. 2026-11-11 02:38 UTCVendor advisory
  11. 2026-11-11 02:38 UTCGHSA enrichmentGHSA-66mm-25pp-rfff · GitHub severity CRITICAL
  12. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  13. 2026-11-10 03:59 UTCEchelonGraph re-scored
  14. 2026-11-10 03:59 UTCVendor advisory
  15. 2026-11-10 03:59 UTCGHSA enrichmentGHSA-66mm-25pp-rfff · GitHub severity CRITICAL
  16. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  17. 2026-11-09 05:39 UTCEchelonGraph re-scored
  18. 2026-11-09 05:39 UTCVendor advisory
  19. 2026-11-09 05:39 UTCGHSA enrichmentGHSA-66mm-25pp-rfff · GitHub severity CRITICAL
  20. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  21. 2026-11-08 07:19 UTCEchelonGraph re-scored
  22. 2026-11-08 07:19 UTCVendor advisory
  23. 2026-11-08 07:19 UTCGHSA enrichmentGHSA-66mm-25pp-rfff · GitHub severity CRITICAL
  24. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  25. 2026-11-07 08:59 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-07 08:59 UTCVendor advisory
  2. 2026-11-07 08:59 UTCGHSA enrichmentGHSA-66mm-25pp-rfff · GitHub severity CRITICAL
  3. 2026-11-06 18:25 UTCOSV refresh
  4. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  5. 2026-11-06 10:39 UTCEchelonGraph re-scored
  6. 2026-11-06 10:39 UTCVendor advisory
  7. 2026-11-06 10:39 UTCGHSA enrichmentGHSA-66mm-25pp-rfff · GitHub severity CRITICAL
  8. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  9. 2026-11-05 12:19 UTCEchelonGraph re-scored
  10. 2026-11-05 12:19 UTCVendor advisory
  11. 2026-11-05 12:19 UTCGHSA enrichmentGHSA-66mm-25pp-rfff · GitHub severity CRITICAL
  12. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  13. 2026-11-04 13:59 UTCEchelonGraph re-scored
  14. 2026-11-04 13:59 UTCVendor advisory
  15. 2026-11-04 13:59 UTCGHSA enrichmentGHSA-66mm-25pp-rfff · GitHub severity CRITICAL
  16. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  17. 2026-11-03 15:39 UTCVendor advisory
  18. 2026-11-03 15:39 UTCGHSA enrichmentGHSA-66mm-25pp-rfff · GitHub severity CRITICAL
  19. 2026-11-02 17:19 UTCEchelonGraph re-scored
  20. 2026-11-02 17:19 UTCVendor advisory
  21. 2026-11-02 17:19 UTCGHSA enrichmentGHSA-66mm-25pp-rfff · GitHub severity CRITICAL
  22. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  23. 2026-11-01 18:58 UTCEchelonGraph re-scored
  24. 2026-11-01 18:58 UTCVendor advisory
  25. 2026-11-01 18:58 UTCGHSA enrichmentGHSA-66mm-25pp-rfff · GitHub severity CRITICAL
  26. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  27. 2026-11-01 07:38 UTCGHSA enrichmentGHSA-66mm-25pp-rfff · GitHub severity CRITICAL
  28. 2026-10-31 20:39 UTCEchelonGraph re-scored
  29. 2026-10-31 20:39 UTCVendor advisory
  30. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  31. 2026-10-30 22:19 UTCEchelonGraph re-scored
  32. 2026-10-30 22:19 UTCVendor advisory
  33. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  34. 2026-10-29 23:56 UTCEchelonGraph re-scored
  35. 2026-10-29 23:56 UTCVendor advisory
  36. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  37. 2026-10-29 01:36 UTCEchelonGraph re-scored
  38. 2026-10-29 01:36 UTCVendor advisory
  39. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  40. 2026-10-28 03:15 UTCEchelonGraph re-scored
  41. 2026-10-28 03:15 UTCVendor advisory
  42. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  43. 2026-10-27 04:45 UTCEchelonGraph re-scored
  44. 2026-10-27 04:45 UTCVendor advisory
  45. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  46. 2026-10-26 02:01 UTCEchelonGraph re-scored
  47. 2026-10-26 02:01 UTCVendor advisory
  48. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  49. 2026-10-25 14:01 UTCEchelonGraph re-scored
  50. 2026-10-25 03:41 UTCEchelonGraph re-scored
  51. 2026-10-25 03:41 UTCVendor advisory
  52. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  53. 2026-10-24 05:22 UTCEchelonGraph re-scored
  54. 2026-10-24 05:22 UTCVendor advisory
  55. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  56. 2026-10-23 07:02 UTCEchelonGraph re-scored
  57. 2026-10-23 07:02 UTCVendor advisory
  58. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  59. 2026-10-22 08:37 UTCEchelonGraph re-scored
  60. 2026-10-22 08:37 UTCVendor advisory
  61. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  62. 2026-10-21 10:17 UTCEchelonGraph re-scored
  63. 2026-10-21 10:17 UTCVendor advisory
  64. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  65. 2026-10-20 11:57 UTCVendor advisory
  66. 2026-10-19 19:20 UTCEchelonGraph re-scored
  67. 2026-10-19 19:20 UTCVendor advisory
  68. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  69. 2026-10-18 21:00 UTCEchelonGraph re-scored
  70. 2026-10-18 21:00 UTCVendor advisory
  71. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  72. 2026-10-18 03:12 UTCEchelonGraph re-scored
  73. 2026-10-17 22:40 UTCEchelonGraph re-scored
  74. 2026-10-17 22:40 UTCVendor advisory
  75. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.9% · 58th percentile

Frequently asked(5)

What is CVE-2026-77415?
CVE-2026-77415 is a critical-severity vulnerability; its CVE record was published on August 21, 2026. JSONata is a JSON query and transformation language. Prior to 1.8.8 and 2.2.1, crafted JSONata expressions could chain several object-integrity weaknesses to execute arbitrary code. The chain could overwrite $clone to mutate objects through evaluateTransformExpression, expose and deconstruct…
When was the CVE record for CVE-2026-77415 published?
The CVE record for CVE-2026-77415 was published on August 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 12, 2026; the record at its source may have been updated since.
Is CVE-2026-77415 actively exploited?
CVE-2026-77415 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (59th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77415?
CVE-2026-77415 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-77415?
A fix for CVE-2026-77415 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-77415 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-77415

Explore →

Is Your Infrastructure Affected by CVE-2026-77415?

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