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
Trending — Patch released this week
7.4EG
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.4Exploit: None knownExposed: 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)
EG Risk
33(Track)
EG Risk 33/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
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

May 7, 2026

Last Modified

August 27, 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(19)

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

Patch Availability(19)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibgnutlsxx28 (3.7.3-4ubuntu1.9) @ jammy2026-08-27ubuntu
ubuntulibgnutlsxx28 (3.6.13-2ubuntu1.12+esm3) @ focal2026-08-27ubuntu
redhatrhcos-418.94.202608142238-02026-08-26redhat
redhatrhui5/rhua-tp-rhel9:17872412602026-08-24redhat
redhatgnutls-0:3.3.29-9.el7_9.22026-07-22redhat
redhatrhcos-4.19.9.6.202607151909-02026-07-22redhat
redhatgnutls-0:3.7.6-21.el9_2.72026-07-20redhat
redhatgnutls-0:3.8.3-4.el9_4.62026-06-29redhat
redhatlibtasn1-0:4.13-3.el8_4.12026-06-29redhat
redhatlibtasn1-0:4.13-4.el8_8.12026-06-29redhat
redhatlibtasn1-0:4.13-3.el8_6.22026-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.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
gnutls—3.8.13-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
gnutls—3.8.13-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
gnutls—3.8.13-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
gnutls—3.8.13-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
gnutls—3.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 20× in last 7d / 117× 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 279 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 August 27, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 60.8% of all scored CVEs.
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

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