CVE-2026-42012

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in gnutls. A remote attacker could exploit this vulnerability by presenting a specially crafted certificate that contains Uniform Resource Identifier (URI) or Service (SRV) Subject Alternative Names (SANs). This could cause the certificate validation process to incorrectly fall back to checking DNS hostnames against the Common Name (CN), potentially allowing the attacker to spoof legitimate services or intercept sensitive information.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

May 26, 2026

Last Modified

September 1, 2026

Advisory Details (5)

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

2467441 – (CVE-2026-42012) CVE-2026-42012 gnutls: gnutls: Certificate validation bypass due to improper handling of URI and SRV SANs

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

cve-details

https://access.redhat.com/security/cve/CVE-2026-42012
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

Patch Availability(17)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibgnutlsxx28 (3.7.3-4ubuntu1.9) @ jammy2026-09-14ubuntu
ubuntulibgnutlsxx28 (3.6.13-2ubuntu1.12+esm3) @ focal2026-09-14ubuntu
redhatrhui5/rhua-tp-rhel9:17872412602026-08-24redhat
redhatgnutls-0:3.3.29-9.el7_9.22026-07-22redhat
redhatgnutls-0:3.7.6-21.el9_2.72026-07-20redhat
redhatlibtasn1-0:4.13-4.el8_8.12026-06-29redhat
redhatlibtasn1-0:4.13-3.el8_4.12026-06-29redhat
redhatlibtasn1-0:4.13-3.el8_6.22026-06-29redhat
redhatgnutls-0:3.8.3-4.el9_4.62026-06-29redhat
redhatgnutls-0:3.8.3-6.el9_6.42026-06-25redhat
redhatdiscovery/discovery-ui-rhel9:17821669522026-06-24redhat
redhatgnutls-0:3.8.9-9.el10_0.192026-06-16redhat
redhatrhui5/rhua-rhel9:17815257392026-06-16redhat
redhatgnutls-0:3.8.10-4.el10_22026-05-26redhat
redhatgnutls-0:3.6.16-8.el8_10.62026-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 rangeFixed inDependents
gnutls3.8.13-r0
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
gnutls3.8.13-r0
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
gnutls3.8.13-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
gnutls3.8.13-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
gnutls3.8.13-r0
Debian:11(1)
PackageVulnerable rangeFixed inDependents
gnutls283.7.1-5 ... 3.7.1-5+deb11u9 (10 versions)3.7.1-5+deb11u10
Debian:12(1)
PackageVulnerable rangeFixed inDependents
gnutls283.7.9-2 ... 3.7.9-2+deb12u6 (7 versions)3.7.9-2+deb12u7
Debian:13(1)
PackageVulnerable rangeFixed inDependents
gnutls283.8.9-3, 3.8.9-3+deb13u1, 3.8.9-3+deb13u2, 3.8.9-3+deb13u33.8.9-3+deb13u4
Debian:14(1)
PackageVulnerable rangeFixed inDependents
gnutls283.8.10-1 ... 3.8.9-3 (11 versions)3.8.13-1

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

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 9× in last 7d / 64× 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 341 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-42012?
CVE-2026-42012 is a high vulnerability published on May 26, 2026. A flaw was found in gnutls. A remote attacker could exploit this vulnerability by presenting a specially crafted certificate that contains Uniform Resource Identifier (URI) or Service (SRV) Subject Alternative Names (SANs). This could cause the certificate validation process to incorrectly fall…
When was CVE-2026-42012 disclosed?
CVE-2026-42012 was first published in the National Vulnerability Database on May 26, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42012 actively exploited?
CVE-2026-42012 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.3% of all scored CVEs.
What is the CVSS score of CVE-2026-42012?
CVE-2026-42012 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-42012?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42012, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42012

Explore →

Is Your Infrastructure Affected by CVE-2026-42012?

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