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.
CVE-2026-6791
This medium-severity CVE scores 6.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.6
- EG Score
- 6.6(medium)
- EG Risk
- 30(Track)EG Risk 30/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity66% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
August 10, 2026
Last Modified
August 12, 2026
Advisory Details (1)
Auto-updated Aug 10, 202634091 – (CVE-2026-6791) wordepx: unbounded alloca (strndupa) in parse_tilde
https://sourceware.org/bugzilla/show_bug.cgi?id=34091Vendor Advisories for CVE-2026-6791(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | glibc-main-2.43-8.1.hum1 | 2026-08-10 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 27× in last 7d / 40× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 06:27 UTCEG score recompute
- 2026-08-20 06:27 UTCVendor advisory
- 2026-08-20 06:27 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 04:46 UTCEG score recompute
- 2026-08-19 04:46 UTCVendor advisory
- 2026-08-19 04:46 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 03:06 UTCEG score recompute
- 2026-08-18 03:06 UTCVendor advisory
- 2026-08-18 03:06 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 01:25 UTCEG score recompute
- 2026-08-17 01:25 UTCVendor advisory
- 2026-08-17 01:25 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 23:45 UTCEG score recompute
- 2026-08-15 23:45 UTCVendor advisory
- 2026-08-15 23:45 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 22:04 UTCEG score recompute
Show 15 moreShow fewer
- 2026-08-14 22:04 UTCVendor advisory
- 2026-08-14 22:04 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 20:18 UTCVendor advisory
- 2026-08-13 20:18 UTCGHSA enrichment
- 2026-08-12 18:38 UTCEG score recompute
- 2026-08-12 18:38 UTCGHSA enrichment
- 2026-08-12 18:17 UTCEG score recompute
- 2026-08-12 18:17 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 21:07 UTCEG score recompute
- 2026-08-11 21:07 UTCGHSA enrichment
- 2026-08-10 19:27 UTCEG score recompute
- 2026-08-10 18:55 UTCEG score recompute
- 2026-08-10 18:54 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-121
Frequently asked(5)
What is CVE-2026-6791?
When was CVE-2026-6791 disclosed?
Is CVE-2026-6791 actively exploited?
What is the CVSS score of CVE-2026-6791?
How do I remediate CVE-2026-6791?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-6791
Is Your Infrastructure Affected by CVE-2026-6791?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.