GnuTLS EUVD-2026-95205

Exploitation requires the attacker to already control a subordinate Certificate Authority whose certificate carries name constraints intended to restrict it to a permitted domain namespace - this pre-established trusted-CA position is the core prerequisite and is not attainable by an ordinary remote attacker. The vulnerable code path is GnuTLS v3.8.13's incomplete enforcement of X.509 name constraints (RFC 5280 §4.2.1.10 / §6.1.4) during certificate-chain validation, so the target is any relying party using that version to validate chains. Limiting factors: the attacker must operate a constrained intermediate CA (a significant barrier reflected in AC:H), the victim must use the vulnerable GnuTLS version for validation, and impact is confined to abusing trust rather than compromising the GnuTLS host itself; no user interaction is required once a forged certificate is presented.

This is a low-urgency, low-real-risk issue despite its security-relevant nature. The provided CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N = 3.7, Low) reflects high attack complexity and limited impact, and this aligns with the other signals: EPSS is 0.12% (2nd percentile), there is no CISA KEV listing (not actively exploited), and no confirmed public exploit. The signals are therefore consistent - all point to a theoretical/targeted PKI-trust weakness rather than a mass-exploitable flaw. The key limiting factor is the precondition embedded in the description: the attacker must already control a subordinate Certificate Authority that is subject to name constraints - a high-privilege, pre-established trust position that very few attackers possess, which justifies AC:H and explains the low EPSS. One point of tension worth flagging: the official vector rates impact as C:L/I:N/A:N, which understates the real-world consequence - bypassing name-constraint (cross-domain PKI) restrictions to issue unauthorized certificates primarily undermines INTEGRITY of the trust chain and can enable impersonation/MITM, so an integrity impact of N appears low; verify impact scoping with the vendor/NVD. No CWE was assigned and product/version metadata in the feed are placeholders, so some fields are inferred from the description text (GnuTLS 3.8.13) rather than confirmed CPE data.

An attacker who operates a subordinate CA that has been issued with name constraints (intended to limit it to a specific domain namespace) exploits GnuTLS 3.8.13's incomplete name-constraint enforcement to issue a certificate for a domain outside its permitted scope. When a victim relying party validating the chain with vulnerable GnuTLS accepts the forged certificate, the attacker can impersonate the unauthorized domain and intercept or tamper with TLS-protected traffic. No public working exploit is identified, though a referenced GitHub gist may contain technical analysis or proof-of-concept material (unverified).