Skip to main content
VulnerabilityPublished

CVE-2026-132276: facelessuser wcmatch · ReDoS

Affects facelessuser wcmatchSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 11.2 when convenient.

Data as of 20 Nov 2026, 17:20 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.9
Patch
Available – fixed in 11.2
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 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 24 Oct 2026.

What to do

Upgrade facelessuser wcmatch to 11.2.

Affected software

ProductAffectedFixed in
facelessuserwcmatchAffected
  • <11.2
Fixed in
  • 11.2

AI-suggested

Upgrade wcmatch to version 11.2 or later, where this inefficient regular expression complexity issue is fixed. No other mitigation is required as the vulnerability is resolved in the official fix.

Description

CVE-2026-132276 is a vulnerability in the Python library wcmatch prior to version 11.2. It involves inefficient regular expression complexity in wildcard file-name matching functions, causing excessive CPU consumption when matching certain attacker-controlled names against developer-controlled patterns with multiple star wildcards. This can lead to denial of service due to prolonged CPU usage. The issue affects functions like fnmatch.fnmatch(), glob.globmatch(), and filesystem glob scans without non-default flags enabled. The vulnerability is fixed in version 11.2.

References

Community reviews

Loading reviews…