CVE-2026-54891 is an improper enforcement of message integrity vulnerability in Erlang/OTP's ssl application, specifically in the tls_gen_connection module and the function tls_gen_connection:handle_protocol_record/3. During TLS handshake processing, the implementation rejects unexpected APPLICATION_DATA records received in pre-handshake states when operating as a server, but fails to enforce the same check when operating as a client. As a result, a network-positioned attacker can send plaintext TLS APPLICATION_DATA records to a vulnerable client before the handshake completes. Those records are buffered and, if the handshake later completes successfully, are delivered to the client application as though they were authenticated server-originated post-handshake data. The flaw affects OTP from 17.0 before 29.0.3, 28.5.0.3, and 27.3.4.14, corresponding to ssl from 5.3.4 before 11.7.3, 11.6.0.3, and 11.2.12.10. TLS 1.3 is affected starting with OTP 22.0, when TLS 1.3 support was introduced.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
12 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.