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
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 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
27.9%
KEV
Not listed

Published

May 26, 2026

Last Modified

July 22, 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

Vendor Advisories for CVE-2026-42012(16)

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

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibgnutls30t64 (3.8.3-1.1ubuntu3.6) @ noble2026-07-01ubuntu
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.8.10-4.el9_82026-05-26redhat
redhatgnutls-0:3.6.16-8.el8_10.62026-05-26redhat

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(1)

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 8× in last 7d / 52× 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 173 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 July 22, 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 27.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs