CVE-2026-42011

HIGHPre-NVD 7.47.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this week
7.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.4Exploit: None knownExposed services: Not assessed

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.4HIGHmedium confidence
EG Risk
33
EG Risk 33/100

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 (value × EchelonGraph’s weight)
Severity74% × 45%
The EG Score, 7.4 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 7, 2026

Last Modified

October 14, 2026

Advisory Details (2)

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

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
Red HatMentions a patch (unverified)

cve-details

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

Vendor Advisories for CVE-2026-42011(20)

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

Patch Availability(29)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibgnutls30t64 (3.8.12-2ubuntu1.1) @ resolute2026-10-14ubuntu
ubuntulibgnutlsxx28 (3.4.10-4ubuntu1.9+esm4) @ xenial2026-10-14ubuntu
redhatcert-manager/jetstack-cert-manager-rhel9:17913710692026-10-13redhat
redhatcert-manager/cert-manager-operator-rhel9:17917882872026-10-13redhat
redhatcert-manager/jetstack-cert-manager-rhel9:17914597112026-10-13redhat
redhatcert-manager/cert-manager-istio-csr-rhel9:17914597592026-10-13redhat
redhatcert-manager/cert-manager-operator-rhel9:17890290762026-10-13redhat
redhatrhai/base-image-neuron-rhel9:17907035422026-10-01redhat
redhatcert-manager/cert-manager-trust-manager-rhel9:17905985932026-09-28redhat
redhatopenshift/ose-rhel-coreos-9:417.94.202608250221-02026-09-03redhat
redhatopenshift/ose-rhel-coreos-8:412.86.202608241157-02026-09-03redhat
redhatopenshift/ose-rhel-coreos-9:416.94.202608150307-02026-08-31redhat
redhatopenshift/ose-rhel-coreos-9:418.94.202608142238-02026-08-26redhat
redhatrhui5/rhua-tp-rhel9:17872412602026-08-24redhat
redhatgnutls-0:3.3.29-9.el7_9.22026-07-22redhat
redhatopenshift/ose-rhel-coreos-9: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-3.el8_6.22026-06-29redhat
redhatlibtasn1-0:4.13-4.el8_8.12026-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.el9_82026-05-26redhat
redhatgnutls-0:3.8.10-4.el10_22026-05-26redhat
redhatgnutls-0:3.6.16-8.el8_10.62026-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(1)

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

Additional Vendor Advisories

(7)

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 30× in last 7d / 70× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 387 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 287 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2026-42011?
CVE-2026-42011 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-42011 was made public on April 29, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on May 7, 2026. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2026-42011 actively exploited?
CVE-2026-42011 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42011?
CVE-2026-42011 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-42011?
A fix for CVE-2026-42011 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-42011 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-42011

Explore →

Is Your Infrastructure Affected by CVE-2026-42011?

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

Book a Demo →Browse All CVEs