Description
Net::BitTorrent versions through 2.1.0 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.
Published: 2026-06-30
Score: 7.5 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The identified vulnerability in Net::BitTorrent versions through 2.1.0 for Perl, a module released by SANKO, allows remote memory exhaustion by accepting an uncapped peer‑wire message‑length prefix. The receiving routine appends each inbound byte to an input buffer and delays decoding until the buffer holds the full message advertised by the peer. If a peer announces a length prefix of up to about 4 GiB and streams bytes, the buffer grows without limit. Because peer connections are unauthenticated and the module fails to validate the length field, this flaw falls under CWE‑400 (Uncontrolled Resource Consumption) and CWE‑770 (Uncontrolled Memory Allocation). The result is that any malicious peer can cause the downloading process to exhaust available memory, potentially crash or become unresponsive, thereby denying service to legitimate users.

Affected Systems

The affected product is Net::BitTorrent, a Perl module used to build BitTorrent clients, with all releases through version 2.1.0 vulnerable. The official fix is to upgrade to version 2.1.0 or later, as advised by the CNA.

Risk and Exploitability

The attack vector is remote, via the peer‑wire protocol used by BitTorrent peers. Because peer connections are unauthenticated, any malicious peer can initiate the attack. The exploit requires no special privileges or additional software beyond a standard BitTorrent client. The CVSS score of 7.5 denotes a high severity, and, combined with an EPSS below 1% and no KEV listing, the lack of mitigation mechanisms in the library and the potential for large memory consumption make this a high‑risk denial‑of‑service flaw.

Generated by OpenCVE AI on July 31, 2026 at 16:38 UTC.

Remediation

Vendor Solution

Upgrade to version 2.1.0 or later.


OpenCVE Recommended Actions

  • Upgrade to Net::BitTorrent version 2.1.0 or later to mitigate the uncontrolled resource consumption vulnerability (CWE‑400).
  • If an upgrade is not immediately possible, configure the BitTorrent client to terminate or reject peer connections that advertise message lengths exceeding a reasonable limit such as 16 KiB, addressing the unchecked input (CWE‑400).
  • After modifying or upgrading, restart the BitTorrent process and monitor memory usage, setting alerts to trigger automatic restarts when usage approaches capacity, thereby limiting potential memory exhaustion (CWE‑770).

Generated by OpenCVE AI on July 31, 2026 at 16:38 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 20 Jul 2026 07:15:00 +0000

Type Values Removed Values Added
Description 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. Net::BitTorrent versions through 2.1.0 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.
Title Net::BitTorrent versions through 2.0.1 for Perl allow remote memory exhaustion via an uncapped peer-wire message-length prefix Net::BitTorrent versions through 2.1.0 for Perl allow remote memory exhaustion via an uncapped peer-wire message-length prefix
References

Wed, 01 Jul 2026 10:30:00 +0000

Type Values Removed Values Added
First Time appeared Sanko
Sanko net::bittorrent
Vendors & Products Sanko
Sanko net::bittorrent

Tue, 30 Jun 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 30 Jun 2026 11:45:00 +0000

Type Values Removed Values Added
Description 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.
Title Net::BitTorrent versions through 2.0.1 for Perl allow remote memory exhaustion via an uncapped peer-wire message-length prefix
Weaknesses CWE-400
CWE-770
References

Subscriptions

Sanko Net::bittorrent
cve-icon MITRE

Status: PUBLISHED

Assigner: CPANSec

Published:

Updated: 2026-07-20T06:42:34.685Z

Reserved: 2026-06-23T18:20:33.514Z

Link: CVE-2026-57080

cve-icon Vulnrichment

Updated: 2026-06-30T13:48:30.630Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-31T16:45:03Z

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-770

    Allocation of Resources Without Limits or Throttling