CVE-2026-5419

LOWPre-NVD 3.73.7—
EchelonGraph scoreMEDIUM confidence

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-06-01. a secondary CVSS source baseline 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.7Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in gnutls. The PKCS#7 padding check, performed during decryption, was not constant-time. This timing side-channel could allow a remote attacker to potentially leak sensitive information about the padding bytes through observable timing differences. This vulnerability is a form of information disclosure.

CVSS v3
3.7
EG Score
3.7(medium)
EG Risk
17(Track)
EG Risk 17/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
Severity37% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

June 1, 2026

Last Modified

September 1, 2026

References (12)

Vendor Advisories for CVE-2026-5419(11)

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

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibgnutls30t64 (3.8.9-3ubuntu2.2) @ questing2026-09-14ubuntu
redhatrhui5/rhua-tp-rhel9:17872412602026-08-24redhat
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
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.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

(8 across 8 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: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

(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 9× in last 7d / 56× 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 206 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-5419?
CVE-2026-5419 is a low vulnerability published on June 1, 2026. A flaw was found in gnutls. The PKCS#7 padding check, performed during decryption, was not constant-time. This timing side-channel could allow a remote attacker to potentially leak sensitive information about the padding bytes through observable timing differences. This vulnerability is a form of…
When was CVE-2026-5419 disclosed?
CVE-2026-5419 was first published in the National Vulnerability Database on June 1, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5419 actively exploited?
CVE-2026-5419 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 68.2% of all scored CVEs.
What is the CVSS score of CVE-2026-5419?
CVE-2026-5419 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-5419?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5419, 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-5419

Explore →

Is Your Infrastructure Affected by CVE-2026-5419?

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

Start Free Scan →Browse All CVEs