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 — 3 sources updated this week
6.6
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.6Exploit: NoneExposed: 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)
EPSS
4.7%
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(14)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibgnutlsxx28 (3.4.10-4ubuntu1.9+esm4) @ xenial2026-07-17ubuntu
ubuntulibgnutls30t64 (3.8.12-2ubuntu1.1) @ resolute2026-07-17ubuntu
redhatlibtasn1-0:4.13-3.el8_6.22026-06-29redhat
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
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(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 11× in last 7d / 85× 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 110 total refreshes for this CVE.

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

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 4.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.