Home/Research/Post

GHSA-53pm-wgxf-c6qf: wcmatch: Polynomial-time ReDoS when matching untrusted names against multi-star patterns (default flags)

  • Severity: MEDIUM
  • CVE: CVE-2026-132276
  • Ecosystems: pip
  • Packages: wcmatch

# Summary

With default flags, a pattern that contains several `*` wildcards takes polynomial time, O(n^k) for k stars, to reject a crafted file name. The pattern is an ordinary developer constant such as `*_*_*_*_*.csv`; only the string being matched comes from the attacker. A 255-byte file name (the maximum on common filesystems) takes 73 s with `fnmatch.fnmatch()` and 86 s with `glob.globmatch()`. The standard library’s `fnmatch` handles the same input in under a millisecond.

This is different from GHSA-84v8-qmgq-9g88: that advisory covers extglob patterns, while this case needs no flags and no attacker-controlled pattern.

# Details

Every `*` is translated to a lazy `.*?` (`_STAR`, `wcmatch/_wcparse.py:212`; `_PATH_STAR` `[^/]*?`, `:218`), which is emitted in `_handle_star` (`:1405-1424`):

“`text
*_*_*_*_*.csv -> ^(?s:(?=.)(?![.]).*?_.*?_.*?_.*?_.*?\.csv)$
“`

When the subject consists of many `_` and does not end in `.csv`, the regex engine tries every way of splitting it between the stars. CPython fixed the same problem in its own `fnmatch` (bpo-40480) by making every star segment except the last one atomic.

# PoC

“`python
import time, fnmatch as std
from wcmatch import fnmatch, glob

for pat, n in [(‘*_*_*_*.csv’, 255), (‘*_*_*_*.csv’, 400), (‘*_*_*_*_*.csv’, 150),
(‘*_*_*_*_*.csv’, 200), (‘*_*_*_*_*.csv’, 255)]:
name = ‘_’ * n
t = time.perf_counter(); fnmatch.fnmatch(name, pat); w = time.perf_counter() – t
t = time.perf_counter(); std.fnmatchcase(name, pat…

Source: GitHub Security Advisories · 2026-11-20