CVE-2026-77414

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.6% (47th 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-64083 (ENISA EUVD) · GHSA-2943-5xfg-gq5f (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.6%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, the src/jsonata.js environment.lookup function used a bypassable hasOwnProperty check. Crafted expressions could use $hasOwnProperty, $spread, $string, prototype access, and $constructor to reach the object prototype and invoke process.getBuiltinModule with child_process, executing arbitrary 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.6%
EPSS %ILE
47th
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.6% 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 (5)

Auto-updated Oct 3, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub advisoryMentions a patch (unverified)

Arbitrary Code Execution via crafted JSONata expressions · Advisory · jsonata-js/jsonata · GitHub

https://github.com/jsonata-js/jsonata/security/advisories/GHSA-2943-5xfg-gq5f
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 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 59e25144fc3b (jsonata-js/jsonata)

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

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

Vendor Advisories for CVE-2026-77414(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 24× in last 7d / 78× 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 223 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 123 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-77414?
CVE-2026-77414 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, the src/jsonata.js environment.lookup function used a bypassable hasOwnProperty check. Crafted expressions could use $hasOwnProperty, $spread, $string, prototype access, and $constructor to reach the object prototype and…
When was the CVE record for CVE-2026-77414 published?
The CVE record for CVE-2026-77414 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-77414 actively exploited?
CVE-2026-77414 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77414?
CVE-2026-77414 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-77414?
A fix for CVE-2026-77414 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-77414 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-77414

Explore →

Is Your Infrastructure Affected by CVE-2026-77414?

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