GnuTLS CVE-2026-95209

The defect manifests specifically when GnuTLS version 3.8.13 performs X.509 certificate-chain validation and encounters a legitimate CA certificate, which it erroneously rejects - breaking TLS handshakes. The triggering condition is simply running the affected 3.8.13 build in any role that validates certificate chains (client or server). Limiting factors: the issue is tied to this specific version (a regression), is not attacker-crafted per SSVC Exploitation:none, and affects availability of TLS connections rather than enabling code execution or data disclosure; environments on other GnuTLS versions are unaffected.

The signals conflict and point to a reliability defect rather than an attacker-driven vulnerability. The input CVSS of 7.5 (AV:N/AC:L/PR:N/UI:N/A:H) frames this as a remotely triggerable, high-availability-impact issue, yet the description characterizes a functional regression in GnuTLS 3.8.13 where legitimate CA certificates are wrongly rejected - i.e., the software denies service to itself, not something an external actor crafts. CISA's SSVC framework reinforces this: Exploitation is rated 'none' and Technical Impact only 'partial', which sits in tension with the A:H in the input vector. No EPSS score was provided, there is no CISA KEV listing, and no public exploit identified at time of analysis, so there is no evidence of exploitation pressure. SSVC Automatable:yes reflects that any triggering condition would recur consistently, but given Exploitation:none this is better read as a deterministic bug than a scalable attack. Net: treat this as a moderate-severity availability/correctness defect to be fixed by upgrading, not as an urgent actively-exploited threat. Verify the A:H claim and the AV:N attack-vector framing with the vendor, since the description implies a validation regression rather than a remotely weaponizable flaw.

A client or server running GnuTLS 3.8.13 performs a routine TLS handshake, but the library incorrectly rejects an otherwise-valid CA certificate in the chain, causing the handshake to fail and the connection to be denied. Because this stems from a validation regression rather than attacker input, the impact manifests as broad service disruption wherever the affected version is deployed. No public exploit identified at time of analysis, and the gist reference has not been confirmed as working proof-of-concept.