CVE-2026-126765
Low 3.7No known exploitationFix availableDouble free after allocation failure in glob
Record last updated
CVSS score
Low on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 41% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
The glob functions in the GNU C Library versions 2.44 and earlier may free the same heap block twice when a memory allocation fails while glob prepends the directory name to the names it matched. The names already rewritten are freed, but their pointers stay in the result vector, and the error path frees them again with globfree. The allocation must fail after at least one name has been rewritten, so the issue can only be reached when the process is already close to its memory limit, for example under an address space limit (RLIMIT_AS) or on a 32-bit system. The attacker needs control to make the result large enough to make the program or service run out of memory, either by controlling the glob pattern and having knowledge of the filesystem layout or through other means. This issue affects all architectures and ABIs supported by the GNU C Library.
Weakness: CWE-415
Patching and mitigation
- Patch status
- Fix available (source: CVE record (glibc))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- sourceware.org (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| The GNU C Library | glibc | all versions up to and including 2.44 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by glibc
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (glibc)
Vendor guidance and references
- https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=advisories/GLIBC-SA-2026-0032 (opens in a new tab)vendor-advisory
- https://sourceware.org/pipermail/libc-alpha/2026-November/182067.html (opens in a new tab)mailing-list, patch
- http://www.openwall.com/lists/oss-security/2026/11/19/9 (opens in a new tab)
- https://sourceware.org/bugzilla/show_bug.cgi?id=34993 (opens in a new tab)issue-tracking