CVE-2026-5260

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

A flaw was found in libgnutls. A remote attacker, by sending an extremely short premaster secret during an RSA key exchange to a server using an RSA key backed by a PKCS#11 token, could trigger a short heap overread. This memory corruption vulnerability could lead to information disclosure.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
52(Track)
EG Risk 52/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
Severity82% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

May 26, 2026

Last Modified

July 24, 2026

Advisory Details (5)

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

2467450 – (CVE-2026-5260) CVE-2026-5260 gnutls: gnutls: Information disclosure via heap overread in RSA key exchange

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

cve-details

https://access.redhat.com/security/cve/CVE-2026-5260
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-5260(16)

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

Patch Availability(16)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibgnutlsxx28 (3.4.10-4ubuntu1.9+esm3) @ xenial2026-07-26ubuntu
ubuntulibgnutls30t64 (3.8.12-2ubuntu1.1) @ resolute2026-07-26ubuntu
redhatrhcos-4.19.9.6.202607151909-02026-07-22redhat
redhatgnutls-0:3.7.6-21.el9_2.72026-07-20redhat
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-4.el9_4.62026-06-29redhat
redhatlibtasn1-0:4.13-3.el8_4.12026-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.el9_82026-05-26redhat
redhatgnutls-0:3.6.16-8.el8_10.62026-05-26redhat
redhatgnutls-0:3.8.10-4.el10_22026-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(2)

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 17× in last 7d / 60× 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 189 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-5260?
CVE-2026-5260 is a high vulnerability published on May 26, 2026. A flaw was found in libgnutls. A remote attacker, by sending an extremely short premaster secret during an RSA key exchange to a server using an RSA key backed by a PKCS#11 token, could trigger a short heap overread. This memory corruption vulnerability could lead to information disclosure.
When was CVE-2026-5260 disclosed?
CVE-2026-5260 was first published in the National Vulnerability Database on May 26, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5260 actively exploited?
CVE-2026-5260 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 49.6% of all scored CVEs.
What is the CVSS score of CVE-2026-5260?
CVE-2026-5260 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-5260?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5260, 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-5260

Explore →

Is Your Infrastructure Affected by CVE-2026-5260?

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

Start Free Scan →Browse All CVEs