CVE-2026-42010

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.9% (59th percentile of EPSS-scored CVEs). GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 9.8Exploit: None knownExposed services: Not assessed

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
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.9%
EPSS %ILE
59th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

May 7, 2026

Last Modified

October 2, 2026

Advisory Details (12)

Auto-updated Oct 2, 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(20)

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

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibgnutls30t64 (3.8.3-1.1ubuntu3.6) @ noble2026-10-02ubuntu
redhatcert-manager/cert-manager-trust-manager-rhel9:17905985932026-09-28redhat
redhatrhcos-415.92.202609140326-02026-09-28redhat
redhatrhcos-413.92.202609080414-02026-09-17redhat
redhatrhcos-414.92.202609011250-02026-09-14redhat
redhatrhcos-417.94.202608250221-02026-09-03redhat
redhatrhcos-412.86.202608241157-02026-09-03redhat
redhatrhcos-416.94.202608150307-02026-08-31redhat
redhatrhcos-418.94.202608142238-02026-08-26redhat
redhatrhui5/rhua-tp-rhel9:17872412602026-08-24redhat
redhatrhcos-4.19.9.6.202607151909-02026-07-22redhat
redhatgnutls-0:3.7.6-21.el9_2.72026-07-20redhat
redhatrhcos-4.21.9.6.202607011303-02026-07-07redhat
redhatrhcos-4.20.9.6.202607010620-02026-07-07redhat
redhatrhcos-4.22.9.8.202606301732-02026-07-07redhat
redhatrhaiis/vllm-cuda-rhel9:17829510122026-07-06redhat
redhatrhaiis/model-opt-cuda-rhel9:17829510512026-07-06redhat
redhatrhaiis/vllm-rocm-rhel9:17829512442026-07-06redhat
redhatlibtasn1-0:4.13-3.el8_6.22026-06-29redhat
redhatlibtasn1-0:4.13-4.el8_8.12026-06-29redhat
redhatgnutls-0:3.8.3-4.el9_4.62026-06-29redhat
redhatlibtasn1-0:4.13-3.el8_4.12026-06-29redhat
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.6.16-8.el8_10.62026-05-26redhat
redhatgnutls-0:3.8.10-4.el10_22026-05-26redhat
redhatgnutls-0:3.8.10-4.el9_82026-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.

Affected Packages

(9 across 9 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
gnutls—
  • every version up to 3.8.13-r0: fixed in 3.8.13-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
gnutls—
  • every version up to 3.8.13-r0: fixed in 3.8.13-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
gnutls—
  • every version up to 3.8.13-r0: fixed in 3.8.13-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
gnutls—
  • every version up to 3.8.13-r0: fixed in 3.8.13-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
gnutls—
  • every version up to 3.8.13-r0: fixed in 3.8.13-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
gnutls283.7.1-5 ... 3.7.1-5+deb11u9 (10 versions)
  • every version up to 3.7.1-5+deb11u10: fixed in 3.7.1-5+deb11u10
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
gnutls283.7.9-2 ... 3.7.9-2+deb12u6 (7 versions)
  • every version up to 3.7.9-2+deb12u7: fixed in 3.7.9-2+deb12u7
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
gnutls283.8.9-3, 3.8.9-3+deb13u1, 3.8.9-3+deb13u2, 3.8.9-3+deb13u3
  • every version up to 3.8.9-3+deb13u4: fixed in 3.8.9-3+deb13u4
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
gnutls283.8.10-1 ... 3.8.9-3 (11 versions)
  • every version up to 3.8.13-1: fixed in 3.8.13-1
—

Weakness Classification(2)

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

Additional Vendor Advisories

(11)

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 14× in last 7d / 55× 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 467 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

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 on May 7, 2026, with the most recent update on October 2, 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 0.9% probability of exploitation in the next 30 days (59th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42010?
CVE-2026-42010 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-42010?
A fix for CVE-2026-42010 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-42010 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs