CVE-2026-82393

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (49th 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-68883 (ENISA EUVD) · GHSA-vq4v-j7r6-jq4m (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
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.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

pnpm is a package manager. Prior to 10.34.5 and 11.11.0, pnpm accepts a scoped path traversal in a tarball dependency's package.json manifest name because pnpm11/resolving/npm-resolver/src/pickPackage.ts rejects slash characters only for unscoped names. During pnpm install, the unvalidated name reaches raw path joins in pnpm11/installing/deps-resolver/src/resolvePeers.ts, pnpm11/installing/deps-resolver/src/index.ts, and pnpm11/deps/graph-builder/src/lockfileToDepGraph.ts, causing package extraction outside node_modules and allowing attacker-controlled files to overwrite arbitrary filesystem paths even when --ignore-scripts is used. The overwrite can replace shell startup files, Git hooks, or installed package code and lead to code execution. This issue is fixed in versions 10.34.5, and 11.11.0.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 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.6%
EPSS %ILE
49th
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.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-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.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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: 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.

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

August 31, 2026

Last Modified

September 9, 2026

Advisory Details (7)

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

pnpm 11.11

Patch available: pnpm/pnpm v11.11.0

https://github.com/pnpm/pnpm/releases/tag/v11.11.0
GitHub release Patch Available

pnpm 10.34.5

Patch available: pnpm/pnpm v10.34.5

https://github.com/pnpm/pnpm/releases/tag/v10.34.5
GitHub commit

commit 78e29fe5583a (pnpm/pnpm)

Fix landed in pnpm/pnpm commit 78e29fe5583a — awaiting tagged release

https://github.com/pnpm/pnpm/commit/78e29fe5583a1e5d69ea05e414eff310f78d5ed9
GitHub commit

commit 51300fd41c5e (pnpm/pnpm)

Fix landed in pnpm/pnpm commit 51300fd41c5e — awaiting tagged release

https://github.com/pnpm/pnpm/commit/51300fd41c5e4c8f47635108e373cc3d1f324fa7
GitHub pull request

fix(security): backport lockfile & manifest name/slot containment to v10

Fix merged in pnpm/pnpm PR #12890 on 2026-07-09 — awaiting tagged release

https://github.com/pnpm/pnpm/pull/12890
GitHub pull request

fix(security): contain lockfile & manifest package names/slots against path traversal (pnpm + pacquet)

Fix merged in pnpm/pnpm PR #12872 on 2026-07-09 — awaiting tagged release

https://github.com/pnpm/pnpm/pull/12872
GitHub advisoryMentions a patch (unverified)

pnpm: A tarball dependency's manifest `name` escapes node_modules → arbitrary file write/overwrite on install · Advisory · pnpm/pnpm · GitHub

https://github.com/pnpm/pnpm/security/advisories/GHSA-vq4v-j7r6-jq4m

Vendor Advisories for CVE-2026-82393(1)

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

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
pnpm—
  • every version up to 10.34.5: fixed in 10.34.5
  • 11.0.0 up to 11.11.0: fixed in 11.11.0
—

Weakness Classification(3)

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

Data Freshness Timeline

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

Showing the most recent 98 of 99 refreshes 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 1 oldest row on record is not shown and was not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-82393?
CVE-2026-82393 is a high-severity vulnerability; its CVE record was published on August 31, 2026. pnpm is a package manager. Prior to 10.34.5 and 11.11.0, pnpm accepts a scoped path traversal in a tarball dependency's package.json manifest name because pnpm11/resolving/npm-resolver/src/pickPackage.ts rejects slash characters only for unscoped names. During pnpm install, the unvalidated name…
When was the CVE record for CVE-2026-82393 published?
The CVE record for CVE-2026-82393 was published on August 31, 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 September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-82393 actively exploited?
CVE-2026-82393 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82393?
CVE-2026-82393 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82393?
A fix for CVE-2026-82393 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-82393 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-82393

Explore →

Is Your Infrastructure Affected by CVE-2026-82393?

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

Book a Demo →Browse All CVEs