CVE-2026-57080

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-30. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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

Net::BitTorrent versions through 2.0.1 for Perl allow remote memory exhaustion via an uncapped peer-wire message-length prefix.

The peer-wire framing in _process_messages trusts the 4-byte length prefix sent by a connected peer with no upper bound, while receive_data appends every inbound byte to the input buffer. A peer announces a length prefix of up to about 4 GiB and then streams bytes; the decoder waits until the buffer holds the full message before processing it, so the buffer grows without limit.

Peer connections are unauthenticated, so any peer in the swarm exhausts the downloading process's memory. The largest legitimate message is a 16 KiB piece block, so any announced length far above that is anomalous.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
17.7%
KEV
Not listed

Published

June 30, 2026

Last Modified

June 30, 2026

Advisory Details (1)

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

CVE-2026-57080 Net::BitTorrent: peer-wire message-length prefix uncapped -> unbounded memory allocation (remote DoS) · Advisory · sanko/Net-BitTorrent.pm · GitHub

https://github.com/sanko/Net-BitTorrent.pm/security/advisories/GHSA-7jr6-2jf4-6qc4

Vendor Advisories for CVE-2026-57080(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 29× in last 7d / 29× 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 07:00 UTCEG score recompute
  2. 2026-07-07 07:00 UTCGHSA enrichment
  3. 2026-07-06 17:58 UTCEG score recompute
  4. 2026-07-06 17:58 UTCGHSA enrichment
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 04:48 UTCEG score recompute
  8. 2026-07-06 04:48 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 15:41 UTCEG score recompute
  12. 2026-07-05 15:40 UTCGHSA enrichment
  13. 2026-07-05 02:40 UTCEG score recompute
  14. 2026-07-05 02:40 UTCGHSA enrichment
  15. 2026-07-05 02:31 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 13:38 UTCEG score recompute
  18. 2026-07-04 13:38 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-04 00:38 UTCEG score recompute
  22. 2026-07-04 00:37 UTCGHSA enrichment
  23. 2026-07-03 11:33 UTCEG score recompute 7.50
  24. 2026-07-03 11:32 UTCGHSA enrichment
  25. 2026-07-01 15:07 UTCEPSS rescore
Show 4 more
  1. 2026-06-30 14:32 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  2. 2026-06-30 12:32 UTCEG score recompute
  3. 2026-06-30 12:32 UTCGHSA enrichment
  4. 2026-06-30 12:32 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-57080?
CVE-2026-57080 is a high vulnerability published on June 30, 2026. Net::BitTorrent versions through 2.0.1 for Perl allow remote memory exhaustion via an uncapped peer-wire message-length prefix. The peer-wire framing in processmessages trusts the 4-byte length prefix sent by a connected peer with no upper bound, while receive_data appends every inbound byte to the…
When was CVE-2026-57080 disclosed?
CVE-2026-57080 was first published in the National Vulnerability Database 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-57080 actively exploited?
CVE-2026-57080 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-57080?
CVE-2026-57080 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-57080?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57080, 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-57080

Explore →

Is Your Infrastructure Affected by CVE-2026-57080?

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