Is CVE-2026-57082 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-57082 being exploited in the wild.

How severe is CVE-2026-57082?

Informational severity, with a CVSS score of 0, published 30 June 2026.

Which products and versions are affected?

SANKO Net::BitTorrent through 2.0.1.

Is there a fix for CVE-2026-57082?

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-57082 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-57082?

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.

CVE-2026-57082: SANKO Net::BitTorrent predictable PRNG in MSE handshake

CVE-2026-57082 · Severity: info · CVSS 0 · Published 2026-06-30

Net::BitTorrent, a Perl library for BitTorrent communications, uses a weak and predictable method for generating encryption keys. This allows an unauthorized observer on the network to intercept and decrypt supposedly private data transfers. Because the encryption keys are generated using a non-secure random number generator, the protection intended to prevent internet service providers or other third parties from monitoring traffic is effectively bypassed.

Technologies: SANKO Net::BitTorrent. Vendors: SANKO.

Quick answers

Is CVE-2026-57082 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-57082 being exploited in the wild.
How severe is CVE-2026-57082?: Informational severity, with a CVSS score of 0, published 30 June 2026.
Which products and versions are affected?: SANKO Net::BitTorrent through 2.0.1.
Is there a fix for CVE-2026-57082?: 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-57082 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-57082?: 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

Net::BitTorrent (up to v2.0.1) utilizes Perl's built-in rand() function, a non-cryptographic drand48-class generator, to derive 160-bit Diffie-Hellman private keys for Message Stream Encryption (MSE). Because the handshake also transmits cleartext random padding generated from the same PRNG sequence immediately after the private key is drawn, a passive network observer can recover the PRNG state from the padding. This allows the attacker to reconstruct the private key, compute the shared secret using the peer's public key, and derive the RC4 keys to decrypt the entire session. The vulnerability is located in KeyExchange.pm and MSE.pm. As of the advisory, no patch is available, and users are advised to replace rand() with a cryptographic source like Crypt::URandom.

Affected products

SANKO Net::BitTorrent through 2.0.1

Timeline

2026-06-28: advisory: GitHub Security Advisory published by maintainer
2026-06-30: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.