AUGUST 15, 2026
Live Feed
Back to database
Case File

CVE-2026-49457

CRITICAL · CVSS 9.1 Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-08-14 · Last synced 2026-08-15

CyberRota Analysis

AI-Generated

The Erlang QUIC implementation prior to version 1.4.4 is vulnerable due to a lack of server authentication during the TLS 1.3 handshake, allowing a man-in-the-middle attacker to impersonate any server and compromise the confidentiality and integrity of the connection. This vulnerability also affects HTTP/3, as it shares the same client implementation. Organizations utilizing this QUIC client should prioritize upgrading to version 1.4.4 or later to mitigate the risk of unauthorized access and data breaches.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

GitHub PoC Links

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-49457
Severity
CRITICAL
CVSS
9.1
EPSS
N/A

Original NVD Description

erlang_quic is a pure Erlang QUIC implementation. Prior to version 1.4.4, the QUIC client did not authenticate the server during the TLS 1.3 handshake. The CertificateVerify signature was not checked, the certificate chain was not validated, and the hostname was not compared against the certificate, so `verify` was effectively a no-op on the client. A man-in-the-middle on the network path could present any certificate and impersonate any server, defeating the confidentiality and integrity of the connection. HTTP/3 uses the same client and was equally affected. Handshakes authenticated by a PSK (session resumption) are not affected, because the peer is authenticated by the PSK binder and no certificate is sent. This is fixed in 1.4.4. The client now verifies the CertificateVerify signature, validates the certificate chain against the trust store (`cacerts` option, the operating system store by default), and checks the hostname. Client `verify` now defaults to on; set `verify => false` to accept any certificate (for example a self-signed test server). No known workarounds are available before 1.4.4. `verify => true` had no effect, and inspecting the certificate after connecting does not help because without the signature check the peer is never proven to own the certificate it presents.