GnuTLS EUVD-2026-20986

No special conditions-remote unauthenticated exploitation against default configurations of GnuTLS-based TLS services when PSK cipher suites are enabled in the server's TLS configuration. The attack requires only network reachability to a listening TLS port (typically 443/tcp for HTTPS, 636/tcp for LDAPS, or application-specific ports). Exploitation is limited to GnuTLS implementations; services using OpenSSL, NSS, or other TLS libraries are not affected. Attack success requires the target service to accept TLS connections and process PSK extensions during handshake negotiation. If PSK cipher suites are explicitly disabled in server configuration or not compiled into the GnuTLS build, the vulnerable code path is not reached. Default Red Hat Enterprise Linux installations typically include PSK support in GnuTLS builds but many production TLS services use certificate-based authentication exclusively, leaving the vulnerable code dormant. Network-based defenses such as TLS proxies, web application firewalls, or IPS devices positioned in front of origin servers may detect or block malformed handshake messages before reaching vulnerable GnuTLS code.

The CVSS 3.1 base score of 7.5 (High) reflects remote network accessibility (AV:N), low attack complexity (AC:L), no required privileges (PR:N), no user interaction (UI:N), and high availability impact (A:H). However, real-world exploitation likelihood appears limited based on multiple signals. EPSS score of 0.08% places this in the 24th percentile, indicating security researchers assess low probability of active exploitation in the next 30 days. SSVC analysis confirms automatable exploitation but notes zero current exploitation activity and only partial technical impact (availability loss without confidentiality or integrity compromise). No CISA KEV listing and no public exploit code identified at time of analysis. This discrepancy between high CVSS severity and low real-world risk suggests this is a quality-of-service vulnerability rather than a pathway for further compromise. Primary risk is service disruption against internet-facing TLS servers using GnuTLS with PSK-enabled cipher suites, but PSK is uncommon in public-facing deployments compared to certificate-based authentication. Organizations should prioritize patching based on: 1) whether affected systems run GnuTLS-based services with PSK cipher suites enabled, 2) whether those services are internet-accessible, and 3) business criticality of service availability. This is not a data breach risk but could enable targeted DoS campaigns against specific GnuTLS deployments.

An attacker identifies a Red Hat Enterprise Linux server running an internet-accessible service that uses GnuTLS for TLS termination (such as a web server, LDAP directory, or VPN gateway). The attacker crafts a malicious TLS ClientHello message containing a PSK extension with an intentionally invalid binder value and sends it to the target server over the network. When GnuTLS processes the handshake, it attempts to validate the PSK binder, triggers the NULL pointer dereference, and immediately crashes the service process. The attacker can repeat this attack to maintain continuous service disruption or coordinate simultaneous attacks against multiple instances to amplify impact. No public proof-of-concept code identified at time of analysis, but the attack is technically straightforward to implement using standard TLS testing libraries.