Quick answers
- Is CVE-2026-57080 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57080 being exploited in the wild.
- How severe is CVE-2026-57080?
- Informational severity, with a CVSS score of 7.5, published 30 June 2026.
- Which products and versions are affected?
- SANKO Net::BitTorrent through 2.0.1.
- Is there a fix for CVE-2026-57080?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-57080 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-57080?
- Check whether you run SANKO Net::BitTorrent at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A resource exhaustion vulnerability exists in Net::BitTorrent versions through 2.0.1. The '_process_messages' function in the BEP03.pm module trusts a 4-byte length prefix provided by a peer without enforcing an upper bound. An unauthenticated remote attacker can announce a message length of up to 4 GiB; the 'receive_data' function will then append all incoming bytes to the input buffer until the announced length is reached. Because the software waits for the full message before processing, the buffer grows until the process is terminated by the operating system's Out-Of-Memory (OOM) killer. As of the advisory date, no patch is available, and users are advised to manually implement a length check (e.g., 1 MiB) to reject anomalous messages.
Affected products
- SANKO Net::BitTorrent through 2.0.1
Timeline
- 2026-06-28: advisory: GitHub advisory GHSA-7jr6-2jf4-6qc4 published
- 2026-06-30: disclosed: NVD publication date