CVE-2026-42011

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.4Exploit: NoneExposed: 0

A fix is available — apply it.

A flaw was found in gnutls. This vulnerability occurs because permitted name constraints were incorrectly ignored when previous Certificate Authorities (CAs) only had excluded name constraints. A remote attacker could exploit this to bypass critical name constraint checks during certificate validation. This bypass could lead to the acceptance of invalid certificates, potentially enabling spoofing or man-in-the-middle attacks against affected systems.

CVSS v3
7.4
EG Score
7.4(medium)
EPSS
38.3%
KEV
Not listed

Published

May 7, 2026

Last Modified

July 22, 2026

Advisory Details (2)

Auto-updated May 7, 2026
Patch available. Sources: redhat.
redhat

2467437 – (CVE-2026-42011) CVE-2026-42011 gnutls: gnutls: Security bypass due to incorrect name constraint handling

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

cve-details

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

Vendor Advisories for CVE-2026-42011(17)

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
redhatgnutls-0:3.8.9-9.el10_0.192026-06-16redhat
redhatrhui5/rhua-rhel9:17815257392026-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.

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 7× in last 7d / 39× 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 152 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-42011?
CVE-2026-42011 is a high vulnerability published on May 7, 2026. A flaw was found in gnutls. This vulnerability occurs because permitted name constraints were incorrectly ignored when previous Certificate Authorities (CAs) only had excluded name constraints. A remote attacker could exploit this to bypass critical name constraint checks during certificate…
When was CVE-2026-42011 disclosed?
CVE-2026-42011 was first published in the National Vulnerability Database on May 7, 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-42011 actively exploited?
CVE-2026-42011 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 38.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42011?
CVE-2026-42011 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-42011?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42011, 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-42011

Explore →

Is Your Infrastructure Affected by CVE-2026-42011?

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

Start Free Scan →Browse All CVEs