CVE-2026-42010: Gnutls: gnutls: authentication bypass via nul character in username
A flaw was found in gnutls. Servers configured with RSA-PSK (Rivest–Shamir–Adleman – Pre-Shared Key) wrongfully matched usernames containing a NUL character with truncated usernames. A remote attacker could exploit this by sending a specially crafted username, leading to an authentication bypass. This vulnerability allows an attacker to gain unauthorized access by circumventing the authentication process.
Security readout for executives and security teams
Plain-English summary
This is an authentication bypass in GnuTLS when a server uses RSA-PSK authentication. A specially formed username containing a NUL character can be matched as a shorter username, potentially letting an attacker access protected services as another identity.
Executive priority
Treat as a high-priority patching item where GnuTLS RSA-PSK protects sensitive or externally reachable services. It is not currently documented as exploited in the provided sources, but authentication bypass against confidentiality-sensitive systems warrants prompt action.
Technical view
GnuTLS servers configured for RSA-PSK can compare usernames incorrectly when a NUL byte is present, causing truncation-style matching. The issue is tracked as CWE-170 and CWE-626, with CVSS 3.1 score 7.1. Red Hat lists affected gnutls packages across RHEL 8, 9, 10, and selected EUS/AUS/TUS/SAP streams.
Likely exposure
Exposure is most likely on Linux services using Red Hat-packaged GnuTLS with RSA-PSK authentication enabled. Systems with GnuTLS installed but not serving RSA-PSK authentication are less directly exposed based on the provided evidence.
Exploitation context
The bundle describes remote exploitation with low privileges and no user interaction. CISA KEV is false, and the supplied sources do not claim active exploitation or public exploit availability.
Researcher notes
Focus validation on actual RSA-PSK server configurations rather than GnuTLS presence alone. The affected list is Red Hat-centric and includes multiple lifecycle streams. Evidence does not establish impact for every upstream or downstream consumer beyond the supplied affected package data.
Mitigation direction
Apply the relevant Red Hat security advisory updates for each affected RHEL stream.
Prioritize internet-facing or sensitive services that use GnuTLS RSA-PSK authentication.
If updates are delayed, check vendor guidance for supported temporary mitigations.
Review non-Red Hat distributions against their own vendor advisories before assuming exposure or fixes.
Validation and detection
Inventory systems running affected RHEL streams and gnutls package versions.
Identify services configured to use GnuTLS RSA-PSK authentication.
Compare installed package versions against the affected versions and RHSA advisories.
Confirm remediation by verifying updated package versions after patching.
Review authentication logs for unusual failed or unexpected username patterns.
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-170: 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.
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 CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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.
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-170 · source CWE mapping
Improper Null Termination
Improper Null Termination represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Null Byte Interaction Error (Poison Null Byte) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.