CVE-2026-127231 (GCVE-0-2026-127231)

Vulnerability from cvelistv5 – Published: 2026-11-18 23:29 – Updated: 2026-11-18 23:29
VLAI
Title
gnutls: double free in X.509 name constraints deinitialization after failed memory allocation
Summary
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.
CWE
Assigner
gnutls CNA under the redhat root
CNA scorecard – unranked: 3 records in the last 180 days, 10 needed details
References
Impacted products
Vendor Product Version CPE status
GnuTLS Project GnuTLS Affected: 3.8.13 , < 3.8.14 (semver)
guessed Create a notification for this product.
Date Public
2026-11-18 00:00
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageName": "gnutls",
          "product": "GnuTLS",
          "programFiles": [
            "lib/x509/name_constraints.c"
          ],
          "programRoutines": [
            {
              "name": "_gnutls_x509_name_constraints_clear"
            },
            {
              "name": "name_constraints_deinit"
            },
            {
              "name": "name_constraints_node_list_deinit"
            }
          ],
          "repo": "https://gitlab.com/gnutls/gnutls",
          "vendor": "GnuTLS Project",
          "versions": [
            {
              "lessThan": "3.8.14",
              "status": "affected",
              "version": "3.8.13",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Xuqing Yang \u003crigelyoung@icloud.com\u003e"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "Xuqing Yang \u003crigelyoung@icloud.com\u003e"
        }
      ],
      "datePublic": "2026-11-18T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "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."
        }
      ],
      "exploits": [
        {
          "lang": "en",
          "value": "Exploitation has only been observed under precise allocation failure injection."
        }
      ],
      "metrics": [
        {
          "other": {
            "content": {
              "description": "GnuTLS severity rating: Low. Exploitation requires an allocation failure to happen at a specific call during name constraints reinitialization.",
              "justification": [
                "memory-pressure"
              ],
              "namespace": "https://gitlab.com/gnutls/gnutls/-/raw/3.8.14/SECURITY.md",
              "value": "Low"
            },
            "type": "GnuTLS severity rating"
          }
        },
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "availabilityImpact": "HIGH",
            "baseScore": 5.9,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "NONE",
            "integrityImpact": "NONE",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-415",
              "description": "CWE-415: Double Free",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-18T23:29:26.526Z",
        "orgId": "56096609-bc02-44d5-8c89-cc887c27f7bb",
        "shortName": "gnutls"
      },
      "references": [
        {
          "tags": [
            "issue-tracking"
          ],
          "url": "https://gitlab.com/gnutls/gnutls/-/work_items/1906"
        },
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://gnutls.org/security-new.html"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "Backport upstream commit \"x509: make name constraints deinitialization idempotent\", or update to GnuTLS 3.8.14."
        }
      ],
      "source": {
        "advisory": "GNUTLS-SA-2026-11-18-3",
        "discovery": "EXTERNAL",
        "url": "https://gitlab.com/gnutls/gnutls/-/work_items/1906"
      },
      "timeline": [
        {
          "lang": "en",
          "time": "2026-06-15T08:59:40.000Z",
          "value": "reported"
        },
        {
          "lang": "en",
          "time": "2026-08-17T17:19:49.000Z",
          "value": "reproduced"
        },
        {
          "lang": "en",
          "time": "2026-11-18T00:00:00.000Z",
          "value": "made public"
        }
      ],
      "title": "gnutls: double free in X.509 name constraints deinitialization after failed memory allocation",
      "x_generator": {
        "engine": "cvelib 1.8.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "56096609-bc02-44d5-8c89-cc887c27f7bb",
    "assignerShortName": "gnutls",
    "cveId": "CVE-2026-127231",
    "datePublished": "2026-11-18T23:29:26.526Z",
    "dateReserved": "2026-11-12T16:46:54.753Z",
    "dateUpdated": "2026-11-18T23:29:26.526Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "packageName": "gnutls",
                "product": "GnuTLS",
                "programFiles": [
                  "lib/x509/name_constraints.c"
                ],
                "programRoutines": [
                  {
                    "name": "_gnutls_x509_name_constraints_clear"
                  },
                  {
                    "name": "name_constraints_deinit"
                  },
                  {
                    "name": "name_constraints_node_list_deinit"
                  }
                ],
                "repo": "https://gitlab.com/gnutls/gnutls",
                "vendor": "GnuTLS Project",
                "versions": [
                  {
                    "lessThan": "3.8.14",
                    "status": "affected",
                    "version": "3.8.13",
                    "versionType": "semver"
                  }
                ]
              }
            ],
            "source": "56096609-bc02-44d5-8c89-cc887c27f7bb"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "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."
          }
        ],
        "id": "CVE-2026-127231",
        "lastModified": "2026-11-19T00:17:41.717",
        "metrics": {
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "HIGH",
                "attackVector": "NETWORK",
                "availabilityImpact": "HIGH",
                "baseScore": 5.9,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
                "version": "3.1"
              },
              "exploitabilityScore": 2.2,
              "impactScore": 3.6,
              "source": "56096609-bc02-44d5-8c89-cc887c27f7bb",
              "type": "Secondary"
            }
          ]
        },
        "published": "2026-11-19T00:17:41.717",
        "references": [
          {
            "source": "56096609-bc02-44d5-8c89-cc887c27f7bb",
            "url": "https://gitlab.com/gnutls/gnutls/-/work_items/1906"
          },
          {
            "source": "56096609-bc02-44d5-8c89-cc887c27f7bb",
            "url": "https://gnutls.org/security-new.html"
          }
        ],
        "sourceIdentifier": "56096609-bc02-44d5-8c89-cc887c27f7bb",
        "vulnStatus": "Received",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-415"
              }
            ],
            "source": "56096609-bc02-44d5-8c89-cc887c27f7bb",
            "type": "Secondary"
          }
        ]
      }
    }
  }
}


Solutions

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

Exploits

CNA · gnutls
Exploitation has only been observed under precise allocation failure injection.

Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.