Loading vulnerability…
CVE-2026-54891 is an improper message integrity enforcement flaw in the Erlang/OTP ssl application, specifically in the tls_gen_connection module. In tls_gen_connection:handle_protocol_record/3, pre-handshake APPLICATION_DATA records are rejected when the TLS endpoint is operating as a server, but the equivalent validation is not enforced when the endpoint is operating as a client. As a result, a network-positioned attacker can send plaintext APPLICATION_DATA records to a vulnerable TLS client during the handshake phase. 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 issue affects TLS 1.3-capable deployments beginning with OTP 22.0, and more broadly affects OTP from R13B03 before 27.3.4.14, from 28.0 before 28.5.0.3, and from 29.0 before 29.0.3. The injection window is broader for TLS versions earlier than 1.3.
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.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.