ansible-lint · wcmatch: Polynomial-time ReDoS when matching untrusted names against multi-star patterns (default flags)
Affects ansible-lintSource GCVE Database
Not known to be exploited · CVSS 5.9 Medium : upgrade to 26.10.1_1 when convenient.
Data as of 22 Nov 2026, 18:23 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.9 |
|---|
- Patch
- Available – fixed in 26.10.1_1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 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 21 Nov 2026.
What to do
Upgrade ansible-lint to 26.10.1_1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewansible-lintpkg:brew/ansible-lintOther threats | Affected
| Fixed in
|
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 wcmatch version 26.10.1_1 that fixes the ReDoS vulnerability by using atomic groups in the regex translation of '*' wildcards. Users should upgrade to this version or later to mitigate the issue. No other mitigation is indicated or required according to the advisory.
Description
A Regular Expression Denial of Service (ReDoS) vulnerability exists in wcmatch when matching untrusted file names against patterns containing multiple '*' wildcards with default flags. The pattern is developer-controlled, but the input string is attacker-controlled. This causes polynomial-time matching, leading to excessive CPU usage and potential application blocking. The issue affects wcmatch versions from 5.0.0 up to but not including 26.10.1_1. A fix is available in version 26.10.1_1 that changes the regex to use atomic groups, significantly improving performance.
References
- github.com/facelessuser/wcmatch/security/advisories/GHSA-53pm-wgxf-c6qf (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-132276 (opens in a new tab)
- github.com/facelessuser/wcmatch/commit/83491aadde57780330f993620083e979f645c80c (opens in a new tab)
- github.com/facelessuser/wcmatch (opens in a new tab)
- github.com/facelessuser/wcmatch/releases/tag/11.2 (opens in a new tab)