Potential stack-based buffer clash during tilde expansion in wordexp
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: azl3 glibc 2.38-21 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to azl3 glibc 2.38-21 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash.
- ALSA-2026:76777
- ALSA-2026:76781
- ALSA-2026:79281
- openSUSE-SU-2026:11660-1
- openSUSE-SU-2026:21968-1
- RHSA-2026:53069
- RHSA-2026:76777
- RHSA-2026:76781
- RHSA-2026:79281
- RLSA-2026:76777
- RLSA-2026:76781
- RLSA-2026:79281
- SUSE-SU-2026:23738-1
- SUSE-SU-2026:23830-1
- SUSE-SU-2026:23929-1
- SUSE-SU-2026:23934-1
- SUSE-SU-2026:23957-1
- SUSE-SU-2026:4204-1
- SUSE-SU-2026:4250-1
- SUSE-SU-2026:4591-1
- Published
- Aug 10, 2026
- Updated
- Sep 3, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-121
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · glibc
- 6.6
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:L/SA:H/E:U
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (glibc). Independent of NVD's CPE analysis and usually ahead of it.
The GNU C Library glibc
- 2.0 and later · up to and including 2.43affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | glibc | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-all-langpacks | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-benchtests | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-common | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-devel | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-doc | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-gconv-extra | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-langpack-aa | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-langpack-af | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-langpack-agr | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-langpack-ak | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-langpack-am | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-langpack-an | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-langpack-anp | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-langpack-ar | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-langpack-as | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-langpack-ast | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-langpack-ayc | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-langpack-az | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-langpack-be | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-langpack-bem | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-langpack-ber | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-langpack-bg | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
| AlmaLinux:10 | glibc-langpack-bhb | before 2.39-142.el10_2.alma.1 | 2.39-142.el10_2.alma.1 |
+96
Same product
the gnu c library: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-19499Buffer overflow in strfmon and strfmon_l right-justification padding30Monitor
- CVE-2026-86805AT_SECURE programs may load attacker-controlled code via $ORIGIN25Monitor
- CVE-2025-0395When the assert() function in the GNU C Library versions 2.13 to 2.40 fails, it does not allocate enough space for the assertion failure mes24Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-8058Jul 23, 2025 · The regcomp function in the GNU C library version from 2.4 to 2.41 is
subject to a double free if some previous allocation fails.23Monitor
- Later →CVE-2026-18374Aug 27, 2026 · Passing an effectively empty string to the `,ccs=` syntax extension of the mode argument in the `fopen` function in the GNU C Library versio19Monitor
- Later →CVE-2026-89092Sep 10, 2026 · Stack overflow in nscd due to unbounded alloca use16Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 glibc 2.38-21 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| almalinux:compat-libpthread-nonshared | 2.28-251.el8_10.43 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:glibc | 2.28-251.el8_10.43 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:glibc-all-langpacks | 2.28-251.el8_10.43 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:glibc-benchtests | 2.28-251.el8_10.43 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:glibc-common | 2.28-251.el8_10.43 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:glibc-devel | 2.28-251.el8_10.43 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:glibc-doc | 2.28-251.el8_10.43 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:glibc-gconv-extra | 2.28-251.el8_10.43 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:glibc-headers | 2.28-251.el8_10.43 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:glibc-langpack-aa | 2.28-251.el8_10.43 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:glibc-langpack-af | 2.28-251.el8_10.43 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:glibc-langpack-agr | 2.28-251.el8_10.43 · AlmaLinux:8 | Package registry (OSV) |
| debian:glibc | 2.43-3 · Debian:14 | Package registry (OSV) |
| opensuse:glibc | 2.44-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:glibc-cross-aarch64-src | 2.40-160000.7.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:glibc-cross-ppc64le-src | 2.40-160000.7.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:glibc-cross-riscv64-src | 2.40-160000.7.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:glibc-cross-s390x-src | 2.40-160000.7.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| red hat:compat-libpthread-nonshared | 0:2.43-8.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:glibc | 0:2.43-8.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:glibc-all-langpacks | 0:2.43-8.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:glibc-benchtests | 0:2.43-8.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:glibc-common | 0:2.43-8.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:glibc-devel | 0:2.43-8.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:glibc-doc | 0:2.43-8.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:glibc-gconv-extra | 0:2.43-8.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:glibc-langpack-aa | 0:2.43-8.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:glibc-langpack-af | 0:2.43-8.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:glibc-langpack-agr | 0:2.43-8.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
+3
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-1954235 days apartStack-based out-of-bounds write in tdelete during tree rebalancing22Monitor
- CVE-2026-9581843 days apartAT_SECURE program buffer overflow via $ORIGIN processing14Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-121 · Stack-based Buffer OverflowCVSS vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:L/SA:H/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.