picotls EUVD-2026-114509

Exploitation requires picotls to be used specifically as the client-side TLS stack - the server-side use is not affected - and the victim client must initiate or complete a TLS handshake with an attacker-controlled or machine-in-the-middle peer. The peer must send a HelloRetryRequest and then a spoofed Hello message that the client processes, triggering the NULL-pointer dereference. Limiting factors that reduce real-world risk: impact is availability-only (process crash/DoS, no code execution or data exposure); the client must be induced to connect to the malicious peer (reflected in UI:R); and only revisions through 44bc503 are affected, with commit a06ca41 and later fixed.

This is a medium-severity, availability-only issue rather than a top-priority emergency. The input CVSS is 6.5 (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H): network-reachable and low-complexity with no privileges required (PR:N, so unauthenticated), but it requires user interaction (UI:R) because a picotls-based client must initiate/complete a handshake with the attacker-controlled or MITM peer, and impact is confined to availability (C:N/I:N) - a NULL-pointer dereference that crashes the consuming process. The vuln.today Decision label is this_month (not act_now/emergency), consistent with a real-but-bounded DoS. No EPSS score, no CISA KEV entry, and no public exploit were provided in the input, so exploitation probability and in-the-wild activity cannot be assessed from the data; the absence of KEV/EPSS is a data gap, not evidence of safety. Net: a legitimate patch-this-cycle issue for anyone running picotls in client mode, but not a widespread-exploitation crisis - the availability-only impact, UI:R dependency on connecting to a hostile peer, and client-only exposure all cap the real-world risk.

An attacker who controls a TLS server, or who can machine-in-the-middle a connection, waits for a picotls-based client to connect, then responds with a HelloRetryRequest followed by a spoofed ServerHello that the client fails to validate, triggering a NULL-pointer dereference. The affected client process crashes, denying service to whatever other work that process was performing. No public exploit was identified in the provided data; the fix PR includes only a cipher-suite-mismatch regression test, not a crash PoC.