CVE-2026-102473: Red Hat Enterprise Linux 6 · ReDoS
Affects Red Hat Enterprise Linux 6Source CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 12 Nov 2026, 23:24 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 5.5 |
|---|
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 29 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Enterprise Linux 6dash | Affected– | Fixed in– |
AI-suggested
Red Hat recommends rebuilding dash with the --enable-fnmatch option to use libc fnmatch for pathname matching, which avoids the vulnerable internal matcher. Until a fix is applied, users should avoid running dash glob patterns or parameter expansions against attacker-controlled filenames containing multiple '*' wildcards. There is no upstream limit on backtracking in the internal matcher, so mitigation relies on configuration changes or avoiding risky inputs.
Description
CVE-2026-102473 is a vulnerability in dash on Red Hat Enterprise Linux 6 where the internal pmatch() matcher uses unbounded recursion for the '*' wildcard when built without libc fnmatch. This can allow a local user to cause excessive CPU consumption by supplying crafted filenames or patterns, resulting in a denial of service. The issue affects non-standard builds that disable libc fnmatch, while standard builds using glibc pattern matching are not significantly exposed. Exploitation requires local access and the ability to influence pattern matching inputs.