CVE-2026-55700

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.3%, top 82% 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.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: 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. From 11.3.0 until 11.5.3, pnpm stage download derived a local filename from registry-controlled package name and version fields. A crafted manifest could escape the selected download directory and overwrite another reachable file. The merged fix validates both fields, derives one safe filename, and verifies the final destination before writing. This vulnerability is fixed in 11.5.3.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
18.3%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 29, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
Patch available. Sources: github, github_pr.
github Patch Available

CAND-PNPM-038: stage download writes outside destination via manifest version traversal · Advisory · pnpm/pnpm · GitHub

https://github.com/pnpm/pnpm/security/advisories/GHSA-v23m-ccfg-pq9h
github_pr

fix: validate staged tarball filenames

Fix merged in pnpm/pnpm PR #12303 on 2026-06-10 — awaiting tagged release

https://github.com/pnpm/pnpm/pull/12303

Vendor Advisories for CVE-2026-55700(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55700?
CVE-2026-55700 is a high vulnerability published on June 25, 2026. pnpm is a package manager. From 11.3.0 until 11.5.3, pnpm stage download derived a local filename from registry-controlled package name and version fields. A crafted manifest could escape the selected download directory and overwrite another reachable file. The merged fix validates both fields,…
When was CVE-2026-55700 disclosed?
CVE-2026-55700 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55700 actively exploited?
CVE-2026-55700 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-55700?
CVE-2026-55700 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-55700?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55700, 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-55700

Explore →

Is Your Infrastructure Affected by CVE-2026-55700?

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

Start Free Scan →Browse All CVEs