CVE-2026-127231

gnutls: double free in X.509 name constraints deinitialization after failed memory allocation

Published Nov 18, 2026 CVSS 3.1 · 5.9 Medium EPSS n/a KEV · Not listed
Description
A double free in the X.509 name constraints enforcement of GnuTLS 3.8.13 on all platforms allows a remote attacker to cause a denial of service (application crash) via a certificate chain containing a NameConstraints extension processed while the application is under memory pressure. When an already populated name constraints object is reinitialized, previously freed list pointers are not cleared, so a memory allocation failure precisely at reinitialization leaves a dangling pointer that is freed again during a later cleanup.

Remediation

Vendor Solution

Backport upstream commit "x509: make name constraints deinitialization idempotent", or update to GnuTLS 3.8.14.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description A double free in the X.509 name constraints enforcement of GnuTLS 3.8.13 on all platforms allows a remote attacker to cause a denial of service (application crash) via a certificate chain containing a NameConstraints extension processed while the application is under memory pressure. When an already populated name constraints object is reinitialized, previously freed list pointers are not cleared, so a memory allocation failure precisely at reinitialization leaves a dangling pointer that is freed again during a later cleanup.
Title gnutls: double free in X.509 name constraints deinitialization after failed memory allocation
Weaknesses CWE-415
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Subscriptions

No data.

Weaknesses

Sources

Status
PUBLISHED
Assigner
gnutls
Published
Updated
Nov 18, 2026, 11:29 PM
Reserved
Nov 12, 2026, 4:46 PM

No data.