Skip to main content
Menu
CVEs

wcmatch denial of service in file name matching via ReDoS

CVE-2026-132276Published , updated

5.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 11.2
Who is exposed
Not reported

Summary

wcmatch, a Python library for wildcard file-name matching, can take prolonged CPU time when it compares an attacker-supplied file name against a pattern with several star wildcards separated by literal text. An attacker can reach this remotely, without logging in, by creating names that the application later matches.

Written by a model

Original description

wcmatch is a Python library for wildcard file-name matching. Prior to 11.2, under the default flags, matching a non-matching attacker-controlled name against an application-supplied pattern containing several star wildcards separated by literals makes the lazy .? and ? segments, including _STAR and _PATH_STAR emitted by _handle_star() in wcmatch/_wcparse.py, backtrack across possible splits, so a single comparison can consume prolonged CPU time. The pattern remains a developer-controlled constant and only the name is attacker-controlled; affected paths include fnmatch.fnmatch(), glob.globmatch(), and filesystem glob scans where another user can create names, without enabling extglob or any non-default flag. This issue is fixed in 11.2.

What to do

Upgrade to a fixed version: 11.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-132276 (wcmatch: Polynomial-time ReDoS when matching untrusted names against multi-star patterns (default flags)), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-132276 (entry last updated 2026-11-20):
Affected:
- facelessuser wcmatch: fixed in 11.2
Fixed versions: 11.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-132276 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132276 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/facelessuser/wcmatch/security/advisories/GHSA-53pm-wgxf-c6qf
- https://github.com/facelessuser/wcmatch/commit/83491aadde57780330f993620083e979f645c80c
- https://github.com/facelessuser/wcmatch/releases/tag/11.2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-132276
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132276"}.

Affected versions

cve.now Index

23Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.9/10CVSS 5.9
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 28 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · facelessuser/wcmatch · Advisory GHSA-53pm-wgxf-c6qf
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-132276
RecordNVD · CVE-2026-132276
Other links 2
RepositoryGitHub · facelessuser/wcmatch · Commit 83491aad
RepositoryGitHub · facelessuser/wcmatch · Release 11.2

Questions about CVE-2026-132276

Is CVE-2026-132276 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-132276?

wcmatch: before 11.2.

Source: cve.now feed data

How do I fix CVE-2026-132276?

Upgrade to a fixed version: 11.2.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.