CVE-2026-104853

MEDIUMPre-NVD 5.85.8
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (6th 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
Trending — 3 sources updated this week

Also known asEUVD-2026-91761 (ENISA EUVD) · GHSA-hrvq-x7jp-36xv (GitHub Security Advisories)Source: ENISA EUVD

5.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Nx is a monorepo solution for TypeScript and polyglot codebases. From 13.10.0 until 22.7.10 and 23.2.1, Nx migration planning reads the nx-migrations.migrations value from a target package manifest without validating that it is a contained relative path. A hostile direct dependency or a package introduced through a trusted package's packageGroup can supply .. segments or an absolute path, causing nx migrate to join an escaping destination onto its temporary directory. The migration archive can then write attacker-controlled bytes outside the temporary directory, while opening the destination stream can truncate an existing writable file even when no archive entry matches. This occurs during migration planning before review of the migration list or use of --run-migrations; the vulnerable installed Nx copy is reached when the normal nx@latest handoff is bypassed with NX_USE_LOCAL, NX_MIGRATE_USE_LOCAL, NX_MIGRATE_CLI_VERSION, --run-id, or fallback after a temporary-install failure. This issue is fixed in versions 22.7.10 and 23.2.1.

CVSS v3
5.8
EG Score
5.8MEDIUMmedium confidence
EG Risk
26
EG Risk 26/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)
Severity58% × 45%
Impact severity (EG Severity): CVSS 5.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.2%
EPSS %ILE
6th
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 (5.8): severity, escalated by confirmed exploitation. This CVE's 5.8 is its impact severity (EG Severity), not escalated.

EG Severity
5.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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 2, 2026

Last Modified

October 2, 2026

Advisory Details (7)

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

23.2.1

Patch available: nrwl/nx 23.2.1

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

22.7.10

Patch available: nrwl/nx 22.7.10

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

commit de37c5ebd185 (nrwl/nx)

Patch available: nrwl/nx 23.2.1 (contains commit de37c5ebd185)

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

commit 95474ab457e8 (nrwl/nx)

Patch available: nrwl/nx 23.3.0-beta.0 (contains commit 95474ab457e8)

https://github.com/nrwl/nx/commit/95474ab457e8e1dbdbefad29040c166105a8fb90
GitHub commit Patch Available

commit 38cd82a0c05e (nrwl/nx)

Patch available: nrwl/nx 22.7.10 (contains commit 38cd82a0c05e)

https://github.com/nrwl/nx/commit/38cd82a0c05e8212e538bdb87ccb198d6504e58f
GitHub pull request Patch Available

fix(core): validate the migrations path before extracting package migrations

Patch available: nrwl/nx 23.3.0-beta.0 (PR #36887 merged 2026-09-03)

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

Path traversal in nx migrate package-migrations extraction · Advisory · nrwl/nx · GitHub

https://github.com/nrwl/nx/security/advisories/GHSA-hrvq-x7jp-36xv

Vendor Advisories for CVE-2026-104853(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
npmnx @ 22.7.10 (fixes >= 13.10.0, < 22.7.10)—ghsa
npmnx @ 23.2.1 (fixes >= 23.0.0, < 23.2.1)—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
nx—
  • 13.10.0 up to 22.7.10: fixed in 22.7.10
  • 23.0.0 up to 23.2.1: fixed in 23.2.1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 46× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-hrvq-x7jp-36xv · GitHub severity MODERATE
  3. 2026-11-01 08:00 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  7. 2026-10-29 14:52 UTCEG score recompute
  8. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-25 14:55 UTCEG score recompute
  13. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-10-23 09:16 UTCEG score recompute
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-10-18 05:09 UTCEG score recompute
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
Show 26 more
  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-10-12 16:40 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  4. 2026-10-11 20:15 UTCEG score recompute
  5. 2026-10-11 18:27 UTCEG score recompute
  6. 2026-10-11 13:54 UTCEG score recompute
  7. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-10-10 14:31 UTCEG score recompute
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-09 15:08 UTCEG score recompute
  12. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-10-08 15:29 UTCEG score recompute
  14. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-10-06 15:55 UTCEG score recompute
  16. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-10-05 16:32 UTCEG score recompute
  19. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-10-03 17:42 UTCEG score recompute
  21. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-10-02 18:14 UTCEG score recompute
  23. 2026-10-02 17:47 UTCEG score recompute
  24. 2026-10-02 17:29 UTCEG score recompute
  25. 2026-10-02 17:00 UTCEG score recomputeFirst assessed: 5.8 MEDIUM
  26. 2026-10-02 17:00 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-104853?
CVE-2026-104853 is a medium-severity vulnerability; its CVE record was published on October 2, 2026. Nx is a monorepo solution for TypeScript and polyglot codebases. From 13.10.0 until 22.7.10 and 23.2.1, Nx migration planning reads the nx-migrations.migrations value from a target package manifest without validating that it is a contained relative path. A hostile direct dependency or a package…
When was the CVE record for CVE-2026-104853 published?
The CVE record for CVE-2026-104853 was published on October 2, 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 2, 2026; the record at its source may have been updated since.
Is CVE-2026-104853 actively exploited?
CVE-2026-104853 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-104853?
CVE-2026-104853 has a CVSS base score of 5.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-104853?
A fix for CVE-2026-104853 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-104853 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-104853

Explore →

Is Your Infrastructure Affected by CVE-2026-104853?

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

Book a Demo →Browse All CVEs