CVE-2026-42011: Gnutls: gnutls: security bypass due to incorrect name constraint handling
A flaw was found in gnutls. This vulnerability occurs because permitted name constraints were incorrectly ignored when previous Certificate Authorities (CAs) only had excluded name constraints. A remote attacker could exploit this to bypass critical name constraint checks during certificate validation. This bypass could lead to the acceptance of invalid certificates, potentially enabling spoofing or man-in-the-middle attacks against affected systems.
Security readout for executives and security teams
Plain-English summary
GnuTLS may accept certificates it should reject when certificate authority name constraints are processed incorrectly. That can weaken trust decisions in TLS and may enable spoofing or man-in-the-middle scenarios. The issue is rated high, but the provided sources do not show known active exploitation.
Executive priority
Treat as a high-priority patching item for systems where TLS trust decisions protect sensitive traffic. It is not shown as exploited here, but successful abuse could undermine authentication and confidentiality.
Technical view
CVE-2026-42011 is a CWE-295 certificate validation flaw in GnuTLS. Permitted name constraints can be ignored when earlier CAs only contain excluded constraints, allowing bypass of critical constraint checks. Red Hat lists affected gnutls packages across RHEL 7 ELS, 8, 9, and 10, with libtasn1 also affected on several RHEL 8 streams.
Likely exposure
Exposure is most likely on Red Hat systems using the listed gnutls or libtasn1 packages, especially TLS clients or services that validate certificate chains from external networks, partners, proxies, or private PKI environments.
Exploitation context
The CVSS vector shows network attackability, no privileges, no user interaction, high confidentiality and integrity impact, and high attack complexity. KEV is false in the bundle, and no cited source here confirms active exploitation.
Researcher notes
Focus review on X.509 name constraint handling in GnuTLS chain validation, especially CA chains mixing excluded-only constraints before permitted constraints. Evidence is limited to the provided CVE, Red Hat, and GnuTLS references.
Mitigation direction
Apply the relevant Red Hat errata for each affected RHEL stream.
Update gnutls and libtasn1 packages where Red Hat marks them affected.
Check vendor guidance for fixed builds before using compensating controls.
Review containers and appliances that may bundle affected Red Hat packages.
Prioritize systems that validate certificates from untrusted or partner-controlled networks.
Validation and detection
Inventory installed gnutls and libtasn1 package versions across RHEL systems.
Map hosts to the affected RHEL products and package builds listed in the bundle.
Confirm vulnerability scanner results reference CVE-2026-42011 after package updates.
Validate TLS clients reject certificates outside permitted name constraints after remediation.
Review certificate validation failure logs for suspicious or unexpected chain behavior.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-295: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
5Timeline events
1ADP providers
19Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-295 · source CWE mapping
Improper Certificate Validation
Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.