CVE-2026-55697

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 97% 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, nvd
Trending — 3 sources updated this weekElevated
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 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.2 and 11.5.3, pnpm can install configDependencies declared in pnpm-workspace.yaml before command dispatch. Before the patch, a repository could declare pacquet or @pnpm/pacquet as a config dependency and pnpm treated that repository-controlled dependency as an install-engine opt-in. During install, pnpm resolved a platform-specific @pacquet/-/pacquet binary from node_modules/.pnpm-config/ and spawned it as the developer or CI user. This vulnerability is fixed in 10.34.2 and 11.5.3.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
2.7%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 30, 2026

Advisory Details (1)

Auto-updated Jun 25, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

CAND-PNPM-097: Repository-controlled configDependencies can select a pacquet native install engine · Advisory · pnpm/pnpm · GitHub

https://github.com/pnpm/pnpm/security/advisories/GHSA-gj8w-mvpf-x27x

Vendor Advisories for CVE-2026-55697(1)

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

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 41× 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-07-06 21:10 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 09:09 UTCEG score recompute
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 21:15 UTCEG score recompute
  8. 2026-07-05 09:20 UTCEG score recompute
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 21:26 UTCEG score recompute
  12. 2026-07-04 09:32 UTCEG score recompute
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-03 21:37 UTCEG score recompute
  16. 2026-07-03 09:43 UTCEG score recompute
  17. 2026-07-02 21:48 UTCEG score recompute
  18. 2026-07-02 09:54 UTCEG score recompute
  19. 2026-07-01 22:00 UTCEG score recompute
  20. 2026-07-01 15:07 UTCEPSS rescore
  21. 2026-07-01 10:00 UTCEG score recompute
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-30 22:06 UTCEG score recompute▲ 1.30
  24. 2026-06-30 20:33 UTCNVD updateCVSS v3 → 8.8
  25. 2026-06-30 10:12 UTCEG score recompute
Show 16 more
  1. 2026-06-29 22:18 UTCEG score recompute
  2. 2026-06-29 14:06 UTCEPSS rescore
  3. 2026-06-29 14:06 UTCEPSS rescore
  4. 2026-06-29 10:24 UTCEG score recompute
  5. 2026-06-28 22:28 UTCEG score recompute
  6. 2026-06-28 14:07 UTCEPSS rescore
  7. 2026-06-28 10:34 UTCEG score recompute
  8. 2026-06-28 04:56 UTCEPSS rescore
  9. 2026-06-28 04:56 UTCEPSS rescore
  10. 2026-06-27 22:40 UTCEG score recompute
  11. 2026-06-27 10:46 UTCEG score recompute
  12. 2026-06-27 03:08 UTCEPSS rescore
  13. 2026-06-26 22:52 UTCEG score recompute
  14. 2026-06-26 10:57 UTCEG score recompute
  15. 2026-06-25 19:50 UTCEG score recompute
  16. 2026-06-25 19:49 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55697?
CVE-2026-55697 is a high vulnerability published on June 25, 2026. pnpm is a package manager. Prior to 10.34.2 and 11.5.3, pnpm can install configDependencies declared in pnpm-workspace.yaml before command dispatch. Before the patch, a repository could declare pacquet or @pnpm/pacquet as a config dependency and pnpm treated that repository-controlled dependency as…
When was CVE-2026-55697 disclosed?
CVE-2026-55697 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55697 actively exploited?
CVE-2026-55697 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-55697?
CVE-2026-55697 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-55697?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55697, 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

Explore the affected products and dependency analysis for CVE-2026-55697

Explore →

Is Your Infrastructure Affected by CVE-2026-55697?

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

Start Free Scan →Browse All CVEs