CVE-2026-55698

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 91% 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
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 persist package-manager bootstrap metadata in the first YAML document of pnpm-lock.yaml. Before the patch, direct pnpm execution trusted an already resolved packageManagerDependencies entry when the committed env lockfile contained matching pnpm and @pnpm/exe versions. A malicious repository could therefore commit package-manager lockfile package records and snapshots that bypassed fresh package-manager resolution, then cause pnpm to install and execute bytes selected by that committed lockfile state during automatic version switching. This vulnerability is fixed in 10.34.2 and 11.5.3.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
9.2%
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-063: Project env lockfile can short-circuit package-manager resolution and execute lockfile-selected pnpm bytes · Advisory · pnpm/pnpm · GitHub

https://github.com/pnpm/pnpm/security/advisories/GHSA-w466-c33r-3gjp

Vendor Advisories for CVE-2026-55698(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 23× in last 7d / 39× 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 19:16 UTCEG score recompute
  2. 2026-07-06 07:58 UTCEG score recompute
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 20:36 UTCEG score recompute
  6. 2026-07-05 09:19 UTCEG score recompute
  7. 2026-07-05 02:31 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 22:04 UTCEG score recompute
  10. 2026-07-04 10:46 UTCEG score recompute
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-03 23:27 UTCEG score recompute
  14. 2026-07-03 12:11 UTCEG score recompute
  15. 2026-07-03 00:44 UTCEG score recompute
  16. 2026-07-02 13:28 UTCEG score recompute
  17. 2026-07-02 02:12 UTCEG score recompute
  18. 2026-07-01 15:07 UTCEPSS rescore
  19. 2026-07-01 14:56 UTCEG score recompute
  20. 2026-07-01 03:41 UTCEG score recompute
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-30 16:24 UTCEG score recompute
  23. 2026-06-30 05:09 UTCEG score recompute
  24. 2026-06-29 17:52 UTCEG score recompute
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 14 more
  1. 2026-06-29 14:06 UTCEPSS rescore
  2. 2026-06-29 06:35 UTCEG score recompute
  3. 2026-06-28 19:18 UTCEG score recompute
  4. 2026-06-28 14:07 UTCEPSS rescore
  5. 2026-06-28 08:02 UTCEG score recompute
  6. 2026-06-28 04:56 UTCEPSS rescore
  7. 2026-06-28 04:56 UTCEPSS rescore
  8. 2026-06-27 20:45 UTCEG score recompute
  9. 2026-06-27 09:29 UTCEG score recompute
  10. 2026-06-27 03:08 UTCEPSS rescore
  11. 2026-06-26 22:13 UTCEG score recompute
  12. 2026-06-26 10:57 UTCEG score recompute
  13. 2026-06-25 19:50 UTCEG score recompute
  14. 2026-06-25 19:49 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55698?
CVE-2026-55698 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 persist package-manager bootstrap metadata in the first YAML document of pnpm-lock.yaml. Before the patch, direct pnpm execution trusted an already resolved packageManagerDependencies entry when the committed env lockfile contained…
When was CVE-2026-55698 disclosed?
CVE-2026-55698 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-55698 actively exploited?
CVE-2026-55698 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-55698?
CVE-2026-55698 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-55698?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55698, 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-55698

Explore →

Is Your Infrastructure Affected by CVE-2026-55698?

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

Start Free Scan →Browse All CVEs