The GNU C Library glibc memory corruption in glob after allocation failure
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
A double free in the glob functions of the GNU C Library (glibc) lets an attacker over the network, without logging in, make a program or service free the same heap memory twice when a memory allocation fails during a glob call. The attacker must be able to make the glob result large enough to exhaust memory, for example by controlling the glob pattern.
Written by a model
Original 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.
What to do
Apply the patch listed under Evidence.
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-126765 (Double free after allocation failure in glob), 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-126765 (entry last updated 2026-11-19):
Affected:
- The GNU C Library glibc: through 2.44
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126765 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126765 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://sourceware.org/git/?p=glibc.git;a=blob_plain;f=advisories/GLIBC-SA-2026-0032
- https://sourceware.org/pipermail/libc-alpha/2026-November/182067.html
- https://sourceware.org/bugzilla/show_bug.cgi?id=34993
- http://www.openwall.com/lists/oss-security/2026/11/19/9
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-126765
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-126765"}.Affected versions
- The GNU C Library glibcthrough 2.44
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach20/20Affects glibc (software on nearly every server, desktop or phone)
- Severity3.7/10CVSS 3.7
- No patch0/5No signal
What would change the score
- Would score about 86 if added to CISA KEV
- Would score about 81 if CISA's SSVC rates exploitation active
- Would score about 46 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-126765 |
| Record | NVD · CVE-2026-126765 |
| Write-ups 2Establishes: Technical detail and context. | |
| Report | sourceware.org · bugzilla/show_bug.cgi?id=34993 |
| Link | openwall.com · lists/oss-security/2026/11/19/9 |
| Other links 2 | |
| Advisory | sourceware.org · git?p=glibc.git;a=blob_plain;f=advisories/GLIBC-SA-2026-0032 |
| Patch | sourceware.org · pipermail/libc-alpha/2026-November/182067.html |
Questions about CVE-2026-126765
Is CVE-2026-126765 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-126765?
glibc: through 2.44.
Source: cve.now feed data
Related
- CVE-2026-19499Buffer overflow in strfmon and strfmon_l right-justification padding
- CVE-2026-5435Potential buffer overflow in ns_sprintrrf TSIG handling path
- CVE-2026-84243gettext: Directory traversal via the LANGUAGE environment variable
- CVE-2026-6791Potential stack-based buffer clash during tilde expansion in wordexp
- CVE-2026-6238Buffer overread in ns_printrrf with corrupted RDATA field
- CVE-2026-86805AT_SECURE programs may load attacker-controlled code via $ORIGIN
No corrections so far. Something wrong on this page? Report an error.