CVE-2026-119282

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (3rd 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

Also known asEUVD-2026-113391 (ENISA EUVD) · GHSA-qm8w-vx34-5j9j (GitHub Security Advisories)Source: ENISA EUVD

7.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Nx is a monorepo solution for TypeScript and polyglot codebases. From 22.0.2 until 22.7.9 and 23.1.2 for @nx/maven, and from 21.0.0 until 22.7.9 and 23.1.2 for @nx/gradle, the plugins' project-graph analyzers launch through a shell and interpolate plugin options from nx.json into command arguments. The @nx/maven targetNamePrefix value and arbitrary @nx/gradle option names or values can therefore be interpreted as shell syntax whenever an nx command constructs the project graph. A user who runs Nx in an attacker-controlled repository or pull request can execute injected commands with the user's privileges, while workspaces that register neither affected plugin are not exposed to this path. Remediation requires upgrading both nx and each affected plugin to matching releases because the plugin fix depends on code in the nx package. This issue is fixed in versions 22.7.9 and 23.1.2.

CVSS
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
33
EG Risk 33/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)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.1%
EPSS %ILE
3rd
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 (7.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.

EG Severity
7.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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 or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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 or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

October 29, 2026

Last Modified

November 3, 2026

Advisory Details (7)

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

23.1.2

Patch available: nrwl/nx 23.1.2

https://github.com/nrwl/nx/releases/tag/23.1.2
GitHub release Patch Available

22.7.9

Patch available: nrwl/nx 22.7.9

https://github.com/nrwl/nx/releases/tag/22.7.9
GitHub commit Patch Available

commit c227f4780b05 (nrwl/nx)

Patch available: nrwl/nx 23.2.0-rc.2 (contains commit c227f4780b05)

https://github.com/nrwl/nx/commit/c227f4780b054c512965c73aa480a48f9f781409
GitHub commit

commit 60196b7cfcff (nrwl/nx)

Fix landed in nrwl/nx commit 60196b7cfcff — awaiting tagged release

https://github.com/nrwl/nx/commit/60196b7cfcffcada35b6b90e53bf1a78d049b548
GitHub commit Patch Available

commit 02c5d59e8dbb (nrwl/nx)

Patch available: nrwl/nx 22.7.10 (contains commit 02c5d59e8dbb)

https://github.com/nrwl/nx/commit/02c5d59e8dbbbe30963c0181c6a22cd8c1190a25
GitHub pull request Patch Available

fix(maven): stop running maven and gradle graph analysis through a shell

Patch available: nrwl/nx 23.2.0-rc.2 (PR #36626 merged 2026-08-14)

https://github.com/nrwl/nx/pull/36626
GitHub advisoryMentions a patch (unverified)

OS command injection via nx.json plugin options in @nx/maven and @nx/gradle · Advisory · nrwl/nx · GitHub

https://github.com/nrwl/nx/security/advisories/GHSA-qm8w-vx34-5j9j

Vendor Advisories for CVE-2026-119282(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@nx/gradle @ 22.7.9 (fixes >= 21.0.0, < 22.7.9)—ghsa
npm@nx/gradle @ 23.1.2 (fixes >= 23.0.0, < 23.1.2)—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

(2 across 1 ecosystem)
npm(2)
PackageVulnerable rangeFix by version rangeDependents
@nx/gradle—
  • 21.0.0 up to 22.7.9: fixed in 22.7.9
  • 23.0.0 up to 23.1.2: fixed in 23.1.2
—
@nx/maven—
  • 22.0.2 up to 22.7.9: fixed in 22.7.9
  • 23.0.0 up to 23.1.2: fixed in 23.1.2
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 22× 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.

  1. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-11-11 03:45 UTCGHSA enrichmentGHSA-qm8w-vx34-5j9j · GitHub severity HIGH
  4. 2026-11-10 18:14 UTCEchelonGraph re-scored
  5. 2026-11-10 18:14 UTCGHSA enrichmentGHSA-qm8w-vx34-5j9j · GitHub severity HIGH
  6. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-11-03 20:14 UTCGHSA enrichmentGHSA-qm8w-vx34-5j9j · GitHub severity HIGH
  14. 2026-11-03 17:26 UTCEchelonGraph re-scored
  15. 2026-11-03 17:26 UTCGHSA enrichmentGHSA-qm8w-vx34-5j9j · GitHub severity HIGH
  16. 2026-11-03 16:57 UTCEchelonGraph re-scored
  17. 2026-11-03 16:57 UTCGHSA enrichmentGHSA-qm8w-vx34-5j9j · GitHub severity HIGH
  18. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  21. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-qm8w-vx34-5j9j · GitHub severity HIGH
  22. 2026-11-01 07:59 UTCEchelonGraph re-scored
  23. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  24. 2026-10-30 19:47 UTCEchelonGraph re-scored
  25. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
Show 4 more
  1. 2026-10-29 22:26 UTCEchelonGraph re-scored
  2. 2026-10-29 22:02 UTCENISA EUVD ID recordedEUVD-2026-113391 · Source: ENISA EUVD
  3. 2026-10-29 21:16 UTCEchelonGraph re-scoredFirst assessed: 7.3 HIGH
  4. 2026-10-29 21:16 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-119282?
CVE-2026-119282 is a high-severity vulnerability; its CVE record was published on October 29, 2026. Nx is a monorepo solution for TypeScript and polyglot codebases. From 22.0.2 until 22.7.9 and 23.1.2 for @nx/maven, and from 21.0.0 until 22.7.9 and 23.1.2 for @nx/gradle, the plugins' project-graph analyzers launch through a shell and interpolate plugin options from nx.json into command arguments.…
When was the CVE record for CVE-2026-119282 published?
The CVE record for CVE-2026-119282 was published on October 29, 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 November 3, 2026; the record at its source may have been updated since.
Is CVE-2026-119282 actively exploited?
CVE-2026-119282 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-119282?
CVE-2026-119282 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-119282?
A fix for CVE-2026-119282 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-119282 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-119282

Explore →

Is Your Infrastructure Affected by CVE-2026-119282?

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

Book a Demo →Browse All CVEs