PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-42014 Red Hat CVE debrief

A use-after-free vulnerability was found in GnuTLS, specifically in the `gnutls_pkcs11_token_set_pin` function. This function is used for changing the Security Officer PIN. The vulnerability occurs when an attacker attempts to change the PIN with a NULL old PIN for a token that lacks a protected authentication path. The CVSS score for this vulnerability is 6.6, with a severity rating of MEDIUM.

Vendor
Red Hat
Product
Red Hat Enterprise Linux 10
CVSS
MEDIUM 6.6
CISA KEV
Not listed in stored evidence
Original CVE published
2026-06-16
Original CVE updated
2026-10-14
Advisory published
2026-06-16
Advisory updated
2026-10-14

Who should care

System administrators and security teams responsible for maintaining systems that use GnuTLS should assess their exposure and prioritize patching or updating GnuTLS to prevent potential attacks.

Why it matters

CVE-2026-42014 is a use-after-free vulnerability in GnuTLS that requires verification of GnuTLS versions, patching priority, and review of system configurations to prevent potential attacks.

  • Verification of GnuTLS version and patching priority
  • Potential for attackers to exploit the vulnerability if left unpatched
  • Need for system administrators to review configurations for protected authentication paths

Technical summary

The `gnutls_pkcs11_token_set_pin` function in GnuTLS is vulnerable to a use-after-free attack when an attacker attempts to change the PIN with a NULL old PIN for a token lacking a protected authentication path. This vulnerability requires verification of GnuTLS versions and configurations to assess exposure. Affected systems may be vulnerable to potential attacks if not patched or updated. System administrators and security teams should prioritize patching or updating GnuTLS to prevent potential attacks. The vulnerability has a CVSS score of 6.6 and a severity rating of MEDIUM.

Defensive priority

Defenders should prioritize verifying the GnuTLS version used in their systems and applying patches or updates as soon as they are available.

Recommended defensive actions

  • Verify GnuTLS version used in systems
  • Apply patches or updates as soon as available
  • Review system configurations for protected authentication paths
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Evidence notes

The vulnerability was reported by an unknown source and is tracked under CVE-2026-42014. The GnuTLS project has acknowledged the issue and provided information about the affected function. Verification of GnuTLS versions and configurations is necessary to assess exposure. System administrators should review system configurations for protected authentication paths and prioritize patching or updating GnuTLS to prevent potential attacks. Evidence limits suggest that further verification is required to confirm affected scope and severity.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-42014 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-42014

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-42014 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-42014

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.