CVE-2026-127231 json
gnutls: double free in X.509 name constraints deinitialization after failed memory allocation
published 1h ago modified 35m ago also EUVD-2026-129375
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
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.
Patch / fix
- GnuTLS Project GnuTLS 3.8.14
Is CVE-2026-127231 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- GnuTLS Project GnuTLS
Classification
- Weakness
-
- CWE-415 Double Free
References
-
gnutls.org
/security-new.html
vendor-advisory
-
gitlab.com
/gnutls/gnutls/-/work_items/1906
issue-tracking
Sources
- CVE List CVE-2026-127231
- NVD CVE-2026-127231
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.