CVE-2026-82392

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

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_pr

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_pr

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 Patch Available

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.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
pnpm—11.11.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-19 05:07 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 04:18 UTCEG score recompute
  4. 2026-09-16 15:05 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 14:16 UTCEG score recompute
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-14 01:02 UTCEG score recompute
  11. 2026-09-13 00:09 UTCEG score recompute
  12. 2026-09-11 23:18 UTCEG score recompute
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 10:49 UTCEG score recompute
  16. 2026-09-10 09:35 UTCEG score recompute
  17. 2026-09-08 23:28 UTCEG score recompute
  18. 2026-09-08 22:01 UTCEPSS rescore
  19. 2026-09-07 21:11 UTCEG score recompute
  20. 2026-09-06 20:22 UTCEG score recompute
  21. 2026-09-06 13:48 UTCEPSS rescore
  22. 2026-09-05 19:32 UTCEG score recompute
  23. 2026-09-05 15:31 UTCEPSS rescore
  24. 2026-09-04 18:43 UTCEG score recompute
  25. 2026-09-04 06:02 UTCEG score recompute
Show 9 more
  1. 2026-09-04 05:07 UTCEPSS rescore
  2. 2026-09-02 16:44 UTCEG score recompute
  3. 2026-09-02 14:12 UTCEPSS rescore
  4. 2026-09-01 15:41 UTCEG score recompute
  5. 2026-09-01 15:04 UTCEG score recompute
  6. 2026-09-01 13:54 UTCEPSS rescore
  7. 2026-08-31 21:21 UTCEG score recompute
  8. 2026-08-31 21:06 UTCEG score recompute
  9. 2026-08-31 21:04 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82392?
CVE-2026-82392 is a high vulnerability 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 CVE-2026-82392 disclosed?
CVE-2026-82392 was first published in the National Vulnerability Database on August 31, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82392 actively exploited?
CVE-2026-82392 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 66.3% of all scored CVEs.
What is the CVSS score of CVE-2026-82392?
CVE-2026-82392 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-82392?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82392, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs