CVE-2026-82392

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-02. A secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-68816 (ENISA EUVD) · GHSA-c59q-g84q-2gj5 (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
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.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

pnpm is a package manager. Prior to 10.34.5 and from 11.0.0 until 11.11.0, pnpm parses the package name from attacker-controlled pnpm-lock.yaml packages keys with dp.parse(depPath).name and uses it without validation in deps/graph-builder/src/lockfileToDepGraph.ts and pnpm11/deps/graph-builder/src/lockfileToDepGraph.ts. The name reaches path.join(modules, pkgName), storeController.importPackage, and pnpm11/lockfile/to-pnp/src/index.ts, allowing package contents to be written outside node_modules when a user runs pnpm install. When dangerouslyAllowAllBuilds or a matching allowBuilds entry permits lifecycle scripts, the escaped package can execute code with the user's privileges. This issue is fixed in versions 10.34.5 and 11.11.0.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 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 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.6%
EPSS %ILE
50th
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.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). 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

August 31, 2026

Last Modified

September 9, 2026

Advisory Details (7)

Auto-updated Aug 31, 2026
Patch available. Sources: github_release, github, github_pr, github_commit.
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)

Virtual store linker path traversal via unvalidated depPath name in lockfileToDepGraph · Advisory · pnpm/pnpm · GitHub

https://github.com/pnpm/pnpm/security/advisories/GHSA-c59q-g84q-2gj5

Vendor Advisories for CVE-2026-82392(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
npmpnpm @ 10.34.5 (fixes < 10.34.5)—ghsa
npmpnpm @ 11.11.0 (fixes >= 11.0.0, < 11.11.0)—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
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(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 33× 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 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). "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 123 rows on record for this CVE, as 99 entries (1 repeat merged).

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 23 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-82392?
CVE-2026-82392 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 from 11.0.0 until 11.11.0, pnpm parses the package name from attacker-controlled pnpm-lock.yaml packages keys with dp.parse(depPath).name and uses it without validation in deps/graph-builder/src/lockfileToDepGraph.ts and…
When was the CVE record for CVE-2026-82392 published?
The CVE record for CVE-2026-82392 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-82392 actively exploited?
CVE-2026-82392 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82392?
CVE-2026-82392 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82392?
A fix for CVE-2026-82392 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-82392 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-82392

Explore →

Is Your Infrastructure Affected by CVE-2026-82392?

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

Book a Demo →Browse All CVEs