Skip to main content
Menu
CVEs

CVE

GnuTLS denial of service in X.509 name constraints parsing

CVE-2026-127231EUVD-2026-129375Published Updated Summary written by a model

5.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 3.8.14
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 3.8.14.

Summary

GnuTLS from the GnuTLS Project has a double free flaw in its X.509 name constraints handling. A remote attacker can trigger it without logging in by sending a certificate chain with a NameConstraints extension while the system is under memory pressure, causing the application to crash.

Original 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.

cve.now Index

23Pcve.now Index 23 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.9/10CVSS 5.9
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 28 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 3.8.14.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-127231 (gnutls: double free in X.509 name constraints deinitialization after failed memory allocation), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-127231 (entry last updated 2026-11-18):
Affected:
- GnuTLS Project GnuTLS: from 3.8.13, fixed in 3.8.14
Fixed versions: 3.8.14.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-127231 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127231 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://gnutls.org/security-new.html
- https://gitlab.com/gnutls/gnutls/-/work_items/1906
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-127231
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-127231"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • gnutls

    From 3.8.13 · fixed in 3.8.14

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Advisorygnutls.org · security-new.html
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-127231
RecordNVD · CVE-2026-127231
Write-ups 1Establishes: Technical detail and context.
Reportgitlab.com · gnutls/gnutls/-/work_items/1906

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-127231

Is CVE-2026-127231 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-127231?

gnutls: from 3.8.13 before 3.8.14.Source: cve.now feed data

How do I fix CVE-2026-127231?

Upgrade to a fixed version: 3.8.14.Source: cve.now feed data

More CVEs