Skip to main content
VulnerabilityPublished

CVE-2026-6791: Glibc · Potential stack-based buffer clash during tilde expansion in wordexp

Affects glibcSource GCVE Database

0
Compare
Authoritative record:CVE-2026-6791· Medium 6.6

Not known to be exploited · CVSS 6.6 Medium : upgrade to 2.39_2 when convenient.

Data as of 18 Nov 2026, 18:50 UTC

CVSS 4.0 base score
6.6Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2.39_2
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade glibc to 2.39_2.

Affected software

ProductAffectedFixed in
Homebrewglibcpkg:brew/glibcOther threatsAffected
  • <2.39_2
Fixed in
  • 2.39_2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in glibc version 2.39_2 that fixes this vulnerability. Users and administrators should upgrade to version 2.39_2 or later to remediate this issue. No other mitigations are specified or required once patched.

Description

CVE-2026-6791 is a critical vulnerability in the GNU C Library (glibc) affecting versions before 2.39_2. It involves a stack-based buffer clash triggered during tilde (~) expansion in the wordexp function when processing excessively long usernames. This occurs because the username is allocated on the stack without bounds checking, potentially exhausting stack space and causing a clash. The issue is fixed in glibc version 2.39_2.

References

Community reviews

Loading reviews…