CVE-2026-42010

CRITICALNVD 9.87.1▼
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-07. NVD baseline CVSS 9.8; sources differ by 2.7.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
7.1(medium)
EPSS
60.2%
KEV
Not listed

Published

May 7, 2026

Last Modified

July 6, 2026

Advisory Details (12)

Auto-updated Jun 30, 2026
Patch available. Sources: redhat.
redhat Patch Available

Affected: Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions and Red Hat Enterprise Linux 8.8 Telecommunications Update Serv

https://access.redhat.com/errata/RHSA-2026:30850
redhat Patch Available

Affected: Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support and Red Hat Enterprise Linux 8.6 Extended Update Support

https://access.redhat.com/errata/RHSA-2026:30849
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.6 Extended Update Support.

https://access.redhat.com/errata/RHSA-2026:30004
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:29197
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.0 Extended Update Support.

https://access.redhat.com/errata/RHSA-2026:26409
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:26319
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:20613
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:20612
redhat Patch Available

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:20611
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:13274
redhat Patch Available

2467289 – (CVE-2026-42010) CVE-2026-42010 gnutls: gnutls: Authentication Bypass via NUL Character in Username

Affected: Red Hat Enterprise Linux 8

https://bugzilla.redhat.com/show_bug.cgi?id=2467289
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-42010

Vendor Advisories for CVE-2026-42010(16)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibgnutlsxx28 (3.7.3-4ubuntu1.9) @ jammy2026-06-28ubuntu
redhatgnutls-0:3.8.3-6.el9_6.42026-06-25redhat
redhatdiscovery/discovery-ui-rhel9:17821669522026-06-24redhat
redhatrhui5/rhua-rhel9:17815257392026-06-16redhat
redhatgnutls-0:3.8.9-9.el10_0.192026-06-16redhat
redhatgnutls-0:3.8.10-4.el9_82026-05-26redhat
redhatgnutls-0:3.8.10-4.el10_22026-05-26redhat
redhatgnutls-0:3.6.16-8.el8_10.62026-05-26redhat
redhatgnutls-main-3.8.13-1.hum12026-05-02redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 12× in last 7d / 108× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 180 total refreshes for this CVE.

  1. 2026-07-06 21:35 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  2. 2026-07-06 19:44 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  3. 2026-07-06 18:21 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  4. 2026-07-06 17:36 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-01 15:06 UTCEPSS rescore
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-29 23:04 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  14. 2026-06-29 21:27 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-29 13:24 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  17. 2026-06-29 12:02 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  18. 2026-06-29 10:04 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  19. 2026-06-29 08:47 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  20. 2026-06-28 14:07 UTCEPSS rescore
  21. 2026-06-28 09:32 UTCEG score recompute
  22. 2026-06-28 09:32 UTCVendor advisory
  23. 2026-06-28 09:32 UTCGHSA enrichment
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-27 14:34 UTCEG score recompute
Show 75 more
  1. 2026-06-27 14:34 UTCVendor advisory
  2. 2026-06-27 14:34 UTCGHSA enrichment
  3. 2026-06-27 03:08 UTCEPSS rescore
  4. 2026-06-26 22:16 UTCEG score recompute
  5. 2026-06-26 22:16 UTCVendor advisory
  6. 2026-06-26 22:16 UTCGHSA enrichment
  7. 2026-06-25 13:49 UTCEPSS rescore
  8. 2026-06-25 13:49 UTCEPSS rescore
  9. 2026-06-24 14:05 UTCEPSS rescore
  10. 2026-06-24 11:53 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  11. 2026-06-23 21:33 UTCEPSS rescore
  12. 2026-06-22 14:25 UTCEPSS rescore
  13. 2026-06-22 14:25 UTCEPSS rescore
  14. 2026-06-21 22:58 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  15. 2026-06-21 14:56 UTCEPSS rescore
  16. 2026-06-21 14:56 UTCEPSS rescore
  17. 2026-06-21 01:59 UTCEPSS rescore
  18. 2026-06-19 19:25 UTCEPSS rescore
  19. 2026-06-18 17:52 UTCEPSS rescore
  20. 2026-06-18 17:52 UTCEPSS rescore
  21. 2026-06-17 17:53 UTCEPSS rescore
  22. 2026-06-17 06:08 UTCEG score recompute
  23. 2026-06-17 06:08 UTCVendor advisory
  24. 2026-06-17 06:08 UTCGHSA enrichment
  25. 2026-06-16 17:52 UTCEPSS rescore
  26. 2026-06-15 17:49 UTCEPSS rescore
  27. 2026-06-15 05:45 UTCEG score recompute
  28. 2026-06-15 05:45 UTCVendor advisory
  29. 2026-06-15 05:45 UTCGHSA enrichment
  30. 2026-06-14 18:30 UTCEG score recompute
  31. 2026-06-14 18:30 UTCVendor advisory
  32. 2026-06-14 18:30 UTCGHSA enrichment
  33. 2026-06-14 07:04 UTCEG score recompute
  34. 2026-06-14 07:04 UTCVendor advisory
  35. 2026-06-14 07:04 UTCGHSA enrichment
  36. 2026-06-13 23:00 UTCEPSS rescore
  37. 2026-06-12 23:12 UTCEPSS rescore
  38. 2026-06-12 23:12 UTCEPSS rescore
  39. 2026-06-12 21:53 UTCEG score recompute
  40. 2026-06-12 21:53 UTCVendor advisory
  41. 2026-06-12 21:53 UTCGHSA enrichment
  42. 2026-06-12 07:19 UTCEG score recompute
  43. 2026-06-12 07:19 UTCVendor advisory
  44. 2026-06-12 07:19 UTCGHSA enrichment
  45. 2026-06-11 20:01 UTCEG score recompute
  46. 2026-06-11 20:01 UTCVendor advisory
  47. 2026-06-11 20:01 UTCGHSA enrichment
  48. 2026-06-11 14:00 UTCEPSS rescore
  49. 2026-06-11 08:45 UTCEG score recompute
  50. 2026-06-11 08:45 UTCVendor advisory
  51. 2026-06-11 08:45 UTCGHSA enrichment
  52. 2026-06-10 22:18 UTCEPSS rescore
  53. 2026-06-10 21:25 UTCEG score recompute
  54. 2026-06-10 21:25 UTCVendor advisory
  55. 2026-06-10 21:25 UTCGHSA enrichment
  56. 2026-06-10 13:22 UTCEPSS rescore
  57. 2026-06-10 13:22 UTCEPSS rescore
  58. 2026-06-10 10:10 UTCEG score recompute
  59. 2026-06-10 10:10 UTCVendor advisory
  60. 2026-06-10 10:10 UTCGHSA enrichment
  61. 2026-06-09 22:55 UTCEG score recompute
  62. 2026-06-09 22:55 UTCVendor advisory
  63. 2026-06-09 22:55 UTCGHSA enrichment
  64. 2026-06-09 09:37 UTCEG score recompute
  65. 2026-06-09 09:37 UTCVendor advisory
  66. 2026-06-09 09:37 UTCGHSA enrichment
  67. 2026-06-08 23:31 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  68. 2026-06-08 22:00 UTCEG score recompute
  69. 2026-06-08 22:00 UTCVendor advisory
  70. 2026-06-08 22:00 UTCGHSA enrichment
  71. 2026-06-08 14:17 UTCEPSS rescore
  72. 2026-06-08 14:17 UTCEPSS rescore
  73. 2026-06-08 10:03 UTCEG score recompute
  74. 2026-06-08 10:03 UTCVendor advisory
  75. 2026-06-08 10:03 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-42010?
CVE-2026-42010 is a critical vulnerability published on May 7, 2026. 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.…
When was CVE-2026-42010 disclosed?
CVE-2026-42010 was first published in the National Vulnerability Database on May 7, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42010 actively exploited?
CVE-2026-42010 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 60.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42010?
CVE-2026-42010 has a CVSS v3 base score of 9.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.1.
How do I remediate CVE-2026-42010?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42010, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-42010

Explore →

Is Your Infrastructure Affected by CVE-2026-42010?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs