PatchSiren cyber security CVE debrief
CVE-2026-57082 SANKO CVE debrief
Net::BitTorrent versions before 2.1.0 for Perl generate the MSE Diffie-Hellman private key with a non-cryptographic PRNG. The MSE handshake derives its 160-bit Diffie-Hellman private key from Perl's rand(), a non-cryptographic drand48-class generator seeded once per process, in KeyExchange.pm. A passive observer of the handshake recovers the PRNG state from the cleartext padding, reconstructs the private key, computes the shared secret from the peer's public key on the wire, derives the RC4 keys, and decrypts the connection. This issue has a medium priority due to the predictability of the PRNG.
- Vendor
- SANKO
- Product
- Net::BitTorrent
- CVSS
- MEDIUM 5.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-06-30
- Original CVE updated
- 2026-07-20
- Advisory published
- 2026-06-30
- Advisory updated
- 2026-07-20
Who should care
Users of Net::BitTorrent versions before 2.1.0 for Perl should update to version 2.1.0 or later to address the predictable PRNG issue. Affected operators include those managing Perl-based systems using Net::BitTorrent. Vulnerability management and security teams should prioritize updates and review compensating controls for exposed systems.
Technical summary
The MSE handshake in Net::BitTorrent versions before 2.1.0 for Perl uses a non-cryptographic PRNG to generate the 160-bit Diffie-Hellman private key. This allows a passive observer to recover the PRNG state, reconstruct the private key, and decrypt the connection. The shared secret and RC4 keys derived from it depend entirely on a predictable PRNG. Affected products include Net::BitTorrent versions before 2.1.0 for Perl. Defenders should review and update any dependent applications or systems.
Defensive priority
Medium priority due to the predictability of the PRNG and potential for passive observers to decrypt connections.
Recommended defensive actions
- Update Net::BitTorrent to version 2.1.0 or later
- Review and update any dependent applications or systems
- Monitor for and respond to potential exploitation attempts
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The CVE record was published on 2026-06-30T12:16:25.737Z and has not been modified since then. The NVD entry is currently Deferred. Evidence is limited to CVE and NVD details. Defenders should verify affected product deployments, review official advisories, and plan updates or mitigations. The predictability of the PRNG used in Net::BitTorrent versions before 2.1.0 for Perl allows a passive observer to recover the PRNG state, reconstruct the private key, and decrypt the connection. This issue affects users of Net::BitTorrent versions before 2.1.0 for Perl.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-57082 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-57082
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-57082 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-57082
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/sanko/Net-BitTorrent.pm/security/advisories/GHSA-g444-x2c5-94hc
9b29abf9-4ab0-4765-b253-1875cd9b441e
-
Source reference
Unverified legacy reference
URL: https://metacpan.org/release/SANKO/Net-BitTorrent-v2.1.0/changes
9b29abf9-4ab0-4765-b253-1875cd9b441e
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.