CVE-2026-102473 json
Dash: dash: super-polynomial backtracking in pmatch when libc fnmatch is disabled
published last mo. modified 4d ago also EUVD-2026-88667
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 0%
- public exploits
- 0
- none known
Summary
A flaw was found in dash. When built without libc fnmatch, the internal pmatch() matcher implements * by unbounded recursion over candidate positions. A local user who can plant filenames, or otherwise feed that matcher, can make a short multi-star pattern such as *.*.*.*.*.tar.gz consume excessive CPU.
Is CVE-2026-102473 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-102473 updated cvss 5.5
dash: dash: Super-polynomial backtracking in pmatch when libc fnmatch is disabled
-
Red Hat Enterprise Linux 6 dashaffected: workaround, no fix planned “Out of support scope”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.10% chance of exploitation in the next 30 days, higher than 0% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Red Hat Red Hat Enterprise Linux 6
Classification
- Weakness
-
- CWE-1333 Inefficient Regular Expression Complexity
References
-
access.redhat.com
/security/cve/CVE-2026-102473
vdb-entry
-
bugzilla.redhat.com
/show_bug.cgi?id=2543005
issue-tracking
Sources
- CVE List CVE-2026-102473
- NVD CVE-2026-102473
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.