CVE-2026-6791

MEDIUMPre-NVD 6.66.6—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
6.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.6
EG Score
6.6MEDIUMmedium confidence
EG Risk
30
EG Risk 30/100CISA SSVC

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 computed
Severity66% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 10, 2026

Last Modified

September 3, 2026

Advisory Details (1)

Auto-updated Aug 10, 2026
Patch available.
generic

34091 – (CVE-2026-6791) wordepx: unbounded alloca (strndupa) in parse_tilde

https://sourceware.org/bugzilla/show_bug.cgi?id=34091

Vendor Advisories for CVE-2026-6791(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntunscd (2.39-0ubuntu8.9) @ noble2026-10-05ubuntu
ubuntunscd (2.43-2ubuntu2.4) @ resolute2026-10-05ubuntu
redhatglibc-main-2.43-8.1.hum12026-08-10redhat

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.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
glibc2.36-10~0 ... 2.44-2 (134 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
glibc2.41-12 ... 2.44-2 (40 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
glibc2.41-12 ... 2.43-2 (27 versions)
  • every version up to 2.43-3: fixed in 2.43-3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 20× in last 7d / 90× 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.

Showing the most recent 100 of 182 total refreshes for this CVE.

  1. 2026-10-05 07:45 UTCEG score recompute
  2. 2026-10-05 07:45 UTCVendor advisory
  3. 2026-10-05 07:45 UTCGHSA enrichment
  4. 2026-10-04 23:22 UTCEPSS rescore
  5. 2026-10-04 04:18 UTCEG score recompute
  6. 2026-10-04 04:18 UTCVendor advisory
  7. 2026-10-04 04:18 UTCGHSA enrichment
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-02 17:56 UTCEPSS rescore
  10. 2026-10-02 09:18 UTCEG score recompute
  11. 2026-10-02 09:18 UTCVendor advisory
  12. 2026-10-02 09:18 UTCGHSA enrichment
  13. 2026-10-01 19:50 UTCEPSS rescore
  14. 2026-09-30 22:25 UTCEG score recompute
  15. 2026-09-30 22:25 UTCVendor advisory
  16. 2026-09-30 22:25 UTCGHSA enrichment
  17. 2026-09-30 15:03 UTCEPSS rescore
  18. 2026-09-29 05:22 UTCEG score recompute
  19. 2026-09-29 05:22 UTCVendor advisory
  20. 2026-09-29 05:21 UTCGHSA enrichment
  21. 2026-09-28 13:52 UTCEPSS rescore
  22. 2026-09-27 13:48 UTCEPSS rescore
  23. 2026-09-27 12:36 UTCEG score recompute
  24. 2026-09-27 12:36 UTCVendor advisory
  25. 2026-09-27 12:36 UTCGHSA enrichment
Show 75 more
  1. 2026-09-26 15:59 UTCEPSS rescore
  2. 2026-09-25 04:00 UTCEG score recompute
  3. 2026-09-25 04:00 UTCVendor advisory
  4. 2026-09-25 04:00 UTCGHSA enrichment
  5. 2026-09-23 17:54 UTCEPSS rescore
  6. 2026-09-23 14:31 UTCEG score recompute
  7. 2026-09-23 14:31 UTCVendor advisory
  8. 2026-09-23 14:31 UTCGHSA enrichment
  9. 2026-09-22 12:49 UTCEG score recompute
  10. 2026-09-22 12:49 UTCVendor advisory
  11. 2026-09-22 12:49 UTCGHSA enrichment
  12. 2026-09-21 21:09 UTCEPSS rescore
  13. 2026-09-21 11:08 UTCEG score recompute
  14. 2026-09-21 11:08 UTCVendor advisory
  15. 2026-09-21 11:08 UTCGHSA enrichment
  16. 2026-09-20 20:16 UTCEPSS rescore
  17. 2026-09-20 05:45 UTCEG score recompute
  18. 2026-09-20 05:45 UTCVendor advisory
  19. 2026-09-20 05:45 UTCGHSA enrichment
  20. 2026-09-19 04:04 UTCEG score recompute
  21. 2026-09-19 04:04 UTCVendor advisory
  22. 2026-09-19 04:04 UTCGHSA enrichment
  23. 2026-09-18 19:28 UTCEPSS rescore
  24. 2026-09-18 02:23 UTCEG score recompute
  25. 2026-09-18 02:23 UTCVendor advisory
  26. 2026-09-18 02:23 UTCGHSA enrichment
  27. 2026-09-17 00:43 UTCEG score recompute
  28. 2026-09-17 00:43 UTCVendor advisory
  29. 2026-09-17 00:43 UTCGHSA enrichment
  30. 2026-09-16 14:08 UTCEPSS rescore
  31. 2026-09-16 05:15 UTCEPSS rescore
  32. 2026-09-15 16:53 UTCEG score recompute
  33. 2026-09-15 16:53 UTCVendor advisory
  34. 2026-09-15 16:53 UTCGHSA enrichment
  35. 2026-09-15 03:12 UTCEPSS rescore
  36. 2026-09-14 15:12 UTCEG score recompute
  37. 2026-09-14 15:12 UTCVendor advisory
  38. 2026-09-14 15:12 UTCGHSA enrichment
  39. 2026-09-13 13:32 UTCEG score recompute
  40. 2026-09-13 13:32 UTCVendor advisory
  41. 2026-09-13 13:32 UTCGHSA enrichment
  42. 2026-09-12 15:02 UTCEPSS rescore
  43. 2026-09-12 11:51 UTCEG score recompute
  44. 2026-09-12 11:51 UTCVendor advisory
  45. 2026-09-12 11:51 UTCGHSA enrichment
  46. 2026-09-11 14:53 UTCEPSS rescore
  47. 2026-09-11 09:12 UTCEG score recompute
  48. 2026-09-11 09:12 UTCVendor advisory
  49. 2026-09-11 09:12 UTCGHSA enrichment
  50. 2026-09-10 09:35 UTCEPSS rescore
  51. 2026-09-10 07:31 UTCVendor advisory
  52. 2026-09-10 07:31 UTCGHSA enrichment
  53. 2026-09-09 05:50 UTCEG score recompute
  54. 2026-09-09 05:50 UTCVendor advisory
  55. 2026-09-09 05:50 UTCGHSA enrichment
  56. 2026-09-08 22:01 UTCEPSS rescore
  57. 2026-09-07 17:14 UTCEG score recompute
  58. 2026-09-07 17:14 UTCVendor advisory
  59. 2026-09-07 17:14 UTCGHSA enrichment
  60. 2026-09-07 16:01 UTCEPSS rescore
  61. 2026-09-06 13:47 UTCEPSS rescore
  62. 2026-09-06 03:35 UTCEG score recompute
  63. 2026-09-06 03:35 UTCVendor advisory
  64. 2026-09-06 03:35 UTCGHSA enrichment
  65. 2026-09-05 15:31 UTCEPSS rescore
  66. 2026-09-05 01:55 UTCEG score recompute
  67. 2026-09-05 01:55 UTCVendor advisory
  68. 2026-09-05 01:55 UTCGHSA enrichment
  69. 2026-09-04 05:07 UTCEPSS rescore
  70. 2026-09-03 16:57 UTCVendor advisory
  71. 2026-09-03 16:57 UTCGHSA enrichment
  72. 2026-09-03 02:09 UTCEG score recompute
  73. 2026-09-03 02:09 UTCVendor advisory
  74. 2026-09-03 02:09 UTCGHSA enrichment
  75. 2026-09-02 14:12 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-6791?
CVE-2026-6791 is a medium vulnerability published on August 10, 2026. 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…
When was CVE-2026-6791 disclosed?
CVE-2026-6791 was first published on August 10, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6791 actively exploited?
CVE-2026-6791 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-6791?
CVE-2026-6791 has a CVSS base score of 6.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-6791?
A fix for CVE-2026-6791 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-6791 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-6791

Explore →

Is Your Infrastructure Affected by CVE-2026-6791?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs