Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessPosition in TLS path as MITM
-
ExploitPresent end-entity cert with contradictory KU/EKU
-
ExecutionGnuTLS fails to reject invalid certificate
-
ImpactObtain sensitive information
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture TOCTOU prevention
|
| Exploitation Conditions | The target application must use GnuTLS 3.8.13 to perform X.509 end-entity certificate verification and rely on Key Usage / Extended Key Usage constraints for trust decisions. The attacker must be able to supply a crafted end-entity certificate containing a contradictory KU/EKU combination that GnuTLS fails to reject, which in practice requires a man-in-the-middle position on the TLS path or control of a server/endpoint the victim connects to. Limiting factors: exploitation is only meaningful where applications depend on KU/EKU enforcement, and the attacker must deliver the malicious certificate into the validation flow rather than act purely remotely with no interaction with the victim's TLS session. |
| Impact | Signals are moderately conflicting. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, 7.5 HIGH) describes a network-reachable, low-complexity, unauthenticated flaw with high confidentiality impact, which looks severe in isolation. However, CISA SSVC tempers this: Exploitation is rated 'none' (no observed exploitation or confirmed POC), Technical Impact is only 'partial', and while Automatable is 'yes', the real-world precondition (an attacker must present a crafted certificate, typically from a MITM or malicious-server position) makes opportunistic mass-exploitation less realistic than AC:L alone suggests. No EPSS score was provided, so exploitation probability cannot be quantified from this data. This is not in CISA KEV and no public exploit is confirmed, though a referenced GitHub gist may contain proof-of-concept material (unverified). Net: a genuine certificate-validation weakness in a widely-used TLS library that warrants patching on a normal remediation cycle, but not emergency/zero-day handling. Note a data inconsistency: CWE-367 (TOCTOU race condition) does not match the described certificate KU/EKU logic flaw - verify the CWE with the vendor. |
| Exploit ScenarioDerived | An attacker in a man-in-the-middle position (or operating a malicious server a GnuTLS client connects to) presents an end-entity X.509 certificate containing a contradictory combination of Key Usage and Extended Key Usage extensions. GnuTLS 3.8.13 fails to reject the certificate as it should, allowing the attacker to be trusted for a purpose the certificate was never valid for and thereby obtain sensitive information from the session. A GitHub gist referenced in the advisory may contain proof-of-concept material, but no confirmed public exploit or active exploitation exists at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 09, 2026
Certificate validation bypass in GnuTLS 3.8.13 allows an attacker who can introduce a crafted end-entity X.509 certificate into the verification path to obtain sensitive information, because the library fails to reject certificates carrying a contradictory combination of Key Usage (KU) and Extended Key Usage (EKU) values. The flaw is remotely reachable without authentication or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N, C:H/I:N/A:N), and CISA's SSVC assessment rates it automatable with partial technical impact; no public exploit has been identified at time of analysis and the issue is not in CISA KEV. Exploitation is meaningful only where a consuming application actually relies on KU/EKU constraints for its trust decisions, and it requires a man-in-the-middle position on the TLS path or control of a server or endpoint the victim connects to.
RemediationAI
No vendor-released patch or fixed version is identified in the provided data, so the primary action is to track the GnuTLS advisory at http://gnutls.com and the upstream repository for a release newer than 3.8.13 and migrate to it as soon as it is published; inventory systems with gnutls-cli --version or package metadata to find anything linking 3.8.13. Because the defect is a missing KU/EKU rejection rather than a crash or memory corruption, a practical compensating control is to re-validate certificate policy after the library call: explicitly parse the end-entity certificate, enforce an application-side EKU allowlist, and reject certificates where KU and EKU are mutually contradictory, accepting the trade-off that duplicated parsing logic can drift from the library's own semantics and may not cover every code path. For high-value TLS channels, certificate or public-key pinning prevents delivery of a rogue certificate at the cost of added operational friction during key and certificate rotation, and narrowing the trust store to a small set of known CAs reduces the pool of certificates an attacker can leverage, although a MITM holding a certificate from an allowed CA would still succeed. Where the affected verification flow is not required, terminating it removes exposure but breaks dependent functionality. Given the absence of KEV and public exploit signals, prioritization can follow the SSVC profile (automatable, partial technical impact) rather than emergency patching; do not treat the linked source permalink as a fix, as it points only to the vulnerable 3.8.13 code.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
GnuTLS is a widely deployed TLS library whose verification routines parse RFC 5280 X.509 certificates and evaluate the Key Usage extension (2.5.29.15) and Extended Key Usage extension (2.5.29.37) to constrain how a certificate may legitimately be used. In version 3.8.13 the logic in lib/x509/verify.c (the referenced lines 1119-1178) fails to reject end-entity certificates asserting a logically contradictory KU/EKU combination, so validation can succeed for a certificate that should be refused; the CVE is classified under CWE-367 (time-of-check time-of-use race condition), which frames the root cause as a state-consistency problem in the verification flow rather than a straightforward parsing error, though the observed effect is a trust-policy enforcement gap. The supplied CPE string (cpe:2.3:a:n/a:n/a:*:*:*:*:*:*:*:*) and the ENISA EUVD affected-version entry ('n/a n/a') provide no finer product granularity, so the reliably identified exposure is the GnuTLS 3.8.13 X.509 end-entity verification path and any application that links it while depending on KU/EKU enforcement.
Know when Gnutls gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Network-reachable TLS certificate validation flaw exploitable without auth or interaction (AV:N/AC:L/PR:N/UI:N); leads to disclosure of sensitive data with no integrity or availability impact.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
3DescriptionCVE.org
An issue in gnutls v.3.8.13 allows an attacker to obtain sensitive information via failing to reject end-entity X.509 certificates that contain a contradictory combination of Key Usage (KU) and Extended Key Usage (EKU)
Executive ViewAI
A certificate validation bypass in GnuTLS 3.8.13 allows an attacker who can insert a crafted X.509 certificate into a verification path to make TLS clients accept a certificate they should have rejected, exposing sensitive data that customers and business systems assume is protected in transit. Because GnuTLS is embedded across Linux distributions, appliances, remote-access concentrators and internal services, most organizations cannot immediately enumerate every affected system, and no vendor patch has been identified, so the exposure persists across trust-critical infrastructure. Leadership should treat this as an unpatched trust-infrastructure risk requiring inventory and interim controls rather than a confirmed incident, since exploitation is only meaningful where an application actually enforces Key Usage and Extended Key Usage constraints and requires an adversary to hold a man-in-the-middle position.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict trust anchors and remove unnecessary intermediate or end-entity certificates from verification paths; enforce Key Usage and Extended Key Usage validation within the consuming application instead of relying solely on GnuTLS; pin certificates or public keys for high-value TLS clients; reduce man-in-the-middle opportunity through network segmentation, egress filtering and strict control of endpoints victims connect to; and temporarily migrate trust-critical services to a TLS stack or build that performs compliant certificate validation.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
A flaw was found in gnutls. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentic
Buffer overflow in the read_server_hello function in lib/gnutls_handshake.c in GnuTLS before 3.1.25, 3.2.x before 3.2.15
An issue was discovered in GnuTLS before 3.6.15. Rated high severity (CVSS 7.5), this vulnerability is remotely exploita
A vulnerability was found in GnuTLS. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no auth
Alpine Linux: gnutls fixed in 3.8.3-r0
Double free vulnerability in libgnutls in GnuTLS before 3.0.14 allows remote attackers to cause a denial of service (app
A timing side-channel in the handling of RSA ClientKeyExchange messages was discovered in GnuTLS. Rated high severity (C
It was discovered in gnutls before version 3.6.7 upstream that there is an uninitialized pointer access in gnutls versio
A vulnerability was found in gnutls versions from 3.5.8 before 3.6.7. Rated high severity (CVSS 7.5), this vulnerability
The asn1_get_length_der function in decoding.c in GNU Libtasn1 before 2.12, as used in GnuTLS before 3.0.16 and other pr
Double free vulnerability in the gnutls_x509_ext_import_proxy function in GnuTLS before 3.3.26 and 3.5.x before 3.5.8 al
gnutls_cipher.c in libgnutls in GnuTLS before 2.12.17 and 3.x before 3.0.15 does not properly handle data encrypted with
EUVD-2026-95206
GHSA-j75v-5pm7-3cg8
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB