Loading story…
CVE-2026-89422 affects Erlang/OTP's TLS 1.3 session-resumption handling, where a client that detects the pre_shared_key extension in ServerHello treats the handshake as resumed and proceeds from EncryptedExtensions directly to the finished-message stage. This path bypasses the normal certificate and certificate-verification processing used for full TLS handshakes.
The issue maps to CWE-322: Key Exchange without Entity Authentication. An attacker able to impersonate or intercept a target TLS endpoint could exploit missing peer-identity validation during PSK resumption to conduct man-in-the-middle or server-impersonation attacks, potentially exposing credentials and application data despite use of encryption. Organizations using Erlang/OTP TLS 1.3 should identify affected deployments and apply vendor remediation or restrict vulnerable resumption paths when available.
See affected versions and whether adversaries are exploiting it.
5 events from the most recent confirmed update back to the earliest known activity.
CVE-2026-89422 was published for an Erlang/OTP TLS 1.3 client flaw in which an unsolicited pre_shared_key extension can cause certificate validation to be bypassed, enabling server impersonation. The issue affects OTP releases from 22.2 before 27.3.4.18, 28.5.0.7, and 29.1.1; those releases contain fixes.
CLASP originally submitted the CWE-322 entry, “Key Exchange without Entity Authentication,” to the CWE catalog.
Erlang/OTP changed its TLS 1.3 client to reject server-selected pre_shared_key identities that were not offered by the client with a fatal illegal_parameter alert. The patch also delays resumption handling until PSK validation succeeds and adds regression coverage for rogue certificate-less servers.
MITRE’s CWE Content Team updated CWE-322 in CWE 4.19, including detection factors, relationships, and weakness ordinalities.
Erlang OTP added preliminary client-side TLS 1.3 session-resumption support using PSK detection in ServerHello. The resumption path transitions from EncryptedExtensions to wait_finished and bypasses the normal certificate-processing path.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
8 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourceosv.dev
Open sourcecna.erlef.org
Open sourcegithub.com
Open sourcegithub.com
Open sourcegithub.com
Open sourcegithub.com
Open sourcecwe.mitre.org
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A critical vulnerability tracked as **`CVE-2026-55953`** affects Erlang/OTP SSL clients using **TLS 1.2 and earlier** as well as **DTLS**, allowing an on-path attacker to bypass server authentication and intercept supposedly secure sessions. The flaw occurs because the client does not verify that the cipher suite selected by the server was actually offered in the `ClientHello`, enabling an attacker to force an anonymous cipher suite and complete the handshake without certificate validation or hostname checking. Once the connection is established, the attacker can read and modify traffic; **TLS 1.3 is not affected** because it already performs the required cipher-suite membership check. The issue affects Erlang/OTP from **`OTP 17.0`** up to the patched releases **`27.3.4.15`**, **`28.5.0.4`**, and **`29.0.4`**, with corresponding SSL fixes in **`11.2.12.11`**, **`11.6.0.4`**, and **`11.7.4`**. Erlang/OTP maintainers addressed the bug in July with code changes to `ssl_handshake.erl` that add a pre-TLS 1.3 client cipher-suite validation check and trigger a fatal `illegal_parameter` alert if the negotiated suite was not advertised by the client. The vulnerability carries a **CVSS 4.0 score of 9.1** and is classified under **`CWE-757`**.
Jul 28, 2026
Two high-severity denial-of-service vulnerabilities in Erlang/OTP's **`ssl`** application allow unauthenticated remote attackers to disrupt secure listeners before authentication completes. **`CVE-2026-55950`** affects the DTLS **`dtls_packet_demux`** component, where a time-of-check/time-of-use race condition can be triggered by rapidly sending multiple DTLS `ClientHello` messages from the same source IP address and port. Because the demultiplexing process is shared across DTLS associations on a listener, a successful crash terminates **all active DTLS sessions** on that listener rather than only the attacker's connection. A second flaw, **`CVE-2026-55952`**, affects **TLS 1.3** servers when malformed `ClientHello` pre-shared key data causes session ticket handling to crash after the software fails to validate that PSK identity and binder lists are the same length. A single crafted request can make TLS 1.3 unusable on an affected listener until the **`ssl`** application is restarted, while TLS 1.2 is not affected. Erlang/OTP maintainers released fixes in **OTP `29.0.3`**, **`28.5.0.3`**, and **`27.3.4.14`**; the DTLS issue was addressed in a GitHub commit that changed logic in **`dtls_packet_demux.erl`** to safely handle existing keys during connection state transitions.
Jul 12, 2026
Erlang/OTP disclosed **CVE-2025-32433** in its SSH implementation as an **unauthenticated remote code execution** vulnerability, tracked in GitHub advisory `GHSA-37cp-fgq5-7wc2`. Public descriptions characterize the issue as a **pre-authentication** flaw tied to improper handling of SSH protocol messages, including malformed `SSH_MSG_CHANNEL_REQUEST` packets, allowing attackers to execute code on exposed Erlang-based SSH servers without valid credentials. Several repositories also describe the weakness as related to missing authentication for a critical function (`CWE-306`). After disclosure, GitHub saw a rapid spread of public exploit material, including proof-of-concept code, remote shell implementations, offensive modules, lab-focused exploit scripts, and later detection tooling. Repositories from multiple authors published exploit variants in Go and other formats, along with testing tools for identifying vulnerable systems, indicating that exploitation knowledge quickly became broadly accessible to both defenders and attackers. The volume and persistence of these repositories suggest that organizations running Erlang/OTP SSH services faced elevated risk of opportunistic scanning and weaponized exploitation soon after the advisory became public.
Jul 23, 2026