Finding and attribution
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.
Product: Gnutls: gnutls: authentication bypass via nul character in username. AI system: AISLE AI-native discovery engine (model/version not disclosed). Team / organization: AISLE.
CVE identifiers: CVE-2026-42010.
AI and human contribution (source account): AISLE’s CVE Discoveries index lists this CVE among those its AI-native engine discovered, and the individual AISLE page says “Discovered by AISLE”. The CNA record credits “Red Hat would like to thank Joshua Rogers (AISLE Research Team) for reporting this issue.”; a credited human name is not itself AI attribution, which rests on AISLE’s page. The model/version and the division of work between the engine and human researchers are not disclosed.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: Public CVE disclosure is dated 2026-04-29. AISLE’s case page timeline shows 2026-05-07, used as the AI-attribution date. The cited sources establish an assigned vulnerability, not exploitation in the wild or zero-day status.
Remediation status: not established. The CVE record does not state a fix or patch reference. Confirm the distribution-specific backport before relying on a version number.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 29 Apr 2026. AI attribution dated 7 May 2026. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: High · highest recorded score 7.1. Documented technical effects: Not available.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2026-42010: CVSS 3.1 · 7.1 (High) ·
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N. redhat (CNA; CVE Program record) · checked 17 Nov 2026.
Technical effects, prerequisites and exploitation evidence are not established here. Missing evidence does not establish absence of exploitation.
Documented fix: The CVE record does not state a fix or patch reference. Confirm the distribution-specific backport before relying on a version number.