The RC4 algorithm, as used in the TLS protocol and SSL protocol, has many single-byte biases, which makes it easier…
No fixed version listed yet.Check the vendor advisory.References ↓
SummaryAI-written · claude-haiku-5-5AI-written · claude-haiku-5-5Written by a language model from the source data on this page. Not reviewed by a person. Generated 29 Oct 2026.
The RC4 stream cipher, as used in the TLS and SSL protocols, contains multiple single-byte biases that weaken its security. A remote attacker can recover plaintext by statistically analysing ciphertext gathered across a large number of sessions that carry the same plaintext, with no authentication or user interaction required.
Official description · CVE.orgSource dataSource dataCopied from an authoritative feed: NVD, CVE.org, CISA KEV, FIRST EPSS or MITRE CTID mappings, or labelled by the annotators of a published dataset. Copied from CVE.org.
The RC4 algorithm, as used in the TLS protocol and SSL protocol, has many single-byte biases, which makes it easier for remote attackers to conduct plaintext-recovery attacks via statistical analysis of ciphertext in a large number of sessions that use the same plaintext.
Priority scorePatchfirst’s 0 to 100 ranking. It adds points for CISA KEV listing, ransomware use, EPSS, threat reports, public exploit code and CVSS. Every CVE page shows the breakdown.Breakdown
29.1 / 100
Exploited
Not confirmed
Reports
0
Tactics
0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Public exploit code (Metasploit) appeared 19 months after disclosure. No confirmed exploitation is recorded.