CVE-2026-42014

MEDIUMPre-NVD 6.66.6
EchelonGraph scoreMEDIUM confidence

Score 6.6 from GitHub Security Advisory published 2026-06-16. a secondary CVSS source baseline 6.6; sources differ by 0.0.

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

A fix is available — apply it.

A flaw was found in GnuTLS. The gnutls_pkcs11_token_set_pin function, used for changing the Security Officer PIN, can lead to a use-after-free vulnerability. This occurs when an attacker attempts to change the PIN with a NULL old PIN for a token that lacks a protected authentication path.

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

Published

June 16, 2026

Last Modified

July 22, 2026

Advisory Details (7)

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

[Security] Use-after-free in gnutls_pkcs11_token_set_pin when retrieving SO PIN (#1766) · Issues · gnutls / GnuTLS · GitLab

https://gitlab.com/gnutls/gnutls/-/issues/1766
redhat

2467451 – (CVE-2026-42014) CVE-2026-42014 gnutls: Fix use-after-free in gnutls_pkcs11_token_set_pin

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

cve-details

https://access.redhat.com/security/cve/CVE-2026-42014
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

Patch Availability(16)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibgnutlsxx28 (3.5.18-1ubuntu1.6+esm4) @ bionic2026-08-05ubuntu
ubuntulibgnutls30t64 (3.8.12-2ubuntu1.1) @ resolute2026-08-05ubuntu
redhatgnutls-0:3.3.29-9.el7_9.22026-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-3.el8_4.12026-06-29redhat
redhatgnutls-0:3.8.3-4.el9_4.62026-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
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.

Affected Packages

(9 across 9 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
gnutls3.8.13-r0
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
gnutls3.8.13-r0
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
gnutls3.8.13-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
gnutls3.8.13-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
gnutls3.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 29× in last 7d / 91× 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 192 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-42014?
CVE-2026-42014 is a medium vulnerability published on June 16, 2026. A flaw was found in GnuTLS. The gnutlspkcs11tokensetpin function, used for changing the Security Officer PIN, can lead to a use-after-free vulnerability. This occurs when an attacker attempts to change the PIN with a NULL old PIN for a token that lacks a protected authentication path.
When was CVE-2026-42014 disclosed?
CVE-2026-42014 was first published in the National Vulnerability Database on June 16, 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-42014 actively exploited?
CVE-2026-42014 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 95.3% of all scored CVEs.
What is the CVSS score of CVE-2026-42014?
CVE-2026-42014 has a CVSS v3 base score of 6.6 (NVD).
How do I remediate CVE-2026-42014?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42014, 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-42014

Explore →

Is Your Infrastructure Affected by CVE-2026-42014?

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