CVE & CISA-KEV Catalog

CVE-2026-57082

MEDIUM
5.9
CVSS v3
NVD

Description

Net::BitTorrent versions before 2.1.0 for Perl generate the MSE Diffie-Hellman private key with a non-cryptographic PRNG. The MSE (Message Stream Encryption) 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. The shared secret and the RC4 keys derived from it (the SHA-1 of "keyA" or "keyB", the shared secret, and the infohash) therefore depend entirely on a predictable PRNG. The same handshake sends, in cleartext, random padding drawn from the same rand() sequence in _random_pad, immediately after the public key and the private-key draw. 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, defeating the passive-observation obfuscation MSE provides.

How to fix

No published remediation has been found for this vulnerability's affected products yet.

Mitigation guidance may be in the linked vendor advisories in the References section below.

TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredNone
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityHigh
IntegrityNone
AvailabilityNone

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploit Intelligence

0.23%probability of exploitation in 30 days
14thpercentile

Low risk: more likely to be exploited than 14% of all known CVEs.

References

Other references2

Related Vulnerabilities

Other CWE-330 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2019-5420Critical9.892%-Fix
CVE-2021-34646Critical9.851%--
CVE-2008-0087High7.532%--
CVE-2017-6026Critical9.132%--
CVE-2018-17888Critical9.830%--
CVE-2020-11901Critical9.021%-Fix

Common questions

How do I fix CVE-2026-57082?

No published fix for CVE-2026-57082 has been found yet. Check the linked vendor advisories for guidance as it becomes available.

Is CVE-2026-57082 being actively exploited?

Not that we know of. CVE-2026-57082 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.23% is the estimated probability that it will be exploited in the next 30 days. That is higher than 14% of all scored CVEs.

How severe is CVE-2026-57082?

CVE-2026-57082 has a CVSS v3 base score of 5.9, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

Embed a live status badge for CVE-2026-57082
CVE-2026-57082 severity badge

Markdown

[![CVE-2026-57082](https://tridentstack.com/cve/badge/CVE-2026-57082.svg)](https://tridentstack.com/cve/CVE-2026-57082)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-57082"><img src="https://tridentstack.com/cve/badge/CVE-2026-57082.svg" alt="CVE-2026-57082"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-07-20.