Wiz rejoint Google Cloud : Faire de la magie ensemble

CVE-2026-132276: 
Python Analyse et atténuation de la vulnérabilité

Aperçu

CVE-2026-132276 is a Regular Expression Denial of Service (ReDoS) vulnerability in the wcmatch Python library for wildcard file-name matching. Prior to version 11.2, matching an attacker-controlled filename against a developer-supplied pattern containing multiple * wildcards separated by literals (e.g., *_*_*_*_*.csv) causes polynomial-time backtracking, allowing a single comparison to consume tens of seconds of CPU time. The vulnerability affects all wcmatch versions up to and including 11.1 under default flags, impacting fnmatch.fnmatch(), glob.globmatch(), and filesystem glob scans. It carries a CVSS v3.1 base score of 5.9 (Medium) (GitHub Advisory).

Détails techniques

The root cause is CWE-1333 (Inefficient Regular Expression Complexity): each * wildcard is translated by _handle_star() in wcmatch/_wcparse.py into a lazy regex segment (.*? as _STAR, or [^/]*? as _PATH_STAR). When multiple such segments appear in sequence, the regex engine must try every possible way to split a non-matching input string across the stars, resulting in O(n^k) complexity for k stars and a name of length n. For example, the pattern *_*_*_*_*.csv becomes ^(?s:(?=.)(?![.]).*?_.*?_.*?_.*?_.*?\.csv)$, which takes ~73 seconds to reject a 255-byte filename of underscores on CPython 3.13, versus under 1 millisecond for the standard library. The attack requires no authentication, no special flags, and no attacker-controlled pattern — only the ability to supply or create a filename that is matched against a multi-star developer pattern (GitHub Advisory, Fix Commit).

Impact

Successful exploitation causes CPU exhaustion on the affected server, blocking a single CPU core for tens of seconds to minutes per crafted filename. Applications vulnerable to this include upload handlers, archive or object-store key filters, and glob/WcMatch directory scans where untrusted users can create filenames. There is no confidentiality or integrity impact; the sole consequence is a Denial of Service that can render the application unresponsive to legitimate users (GitHub Advisory).

Exploitabilité

A proof-of-concept exploit is publicly available in the GitHub Security Advisory, demonstrating that a 255-byte filename of underscore characters causes fnmatch.fnmatch() to take ~72.7 seconds and glob.globmatch() to take ~85.75 seconds, compared to under 1 millisecond for the Python standard library. No authentication or user interaction is required, though exploitation requires the attacker to be able to supply or create a filename that is matched against a vulnerable multi-star pattern. The EPSS score is 0.0 and there is no evidence of in-the-wild exploitation or CISA KEV catalog listing at this time (GitHub Advisory, Feedly).

Étapes d’exploitation

  1. Identify a vulnerable target: Find an application using wcmatch versions prior to 11.2 that matches user-controlled filenames or paths against patterns containing multiple * wildcards separated by literals (e.g., upload handlers, file filters, or directory scanners).
  2. Craft a malicious filename: Construct a filename consisting of repeated underscore (or similar) characters near the filesystem limit (e.g., '_' * 255), which will not match the target pattern but will maximize backtracking.
  3. Submit the crafted filename: Supply the filename to the application — for example, by uploading a file, creating a file in a scanned directory, or passing the name as input to an API that invokes fnmatch.fnmatch(name, '*_*_*_*_*.csv') or glob.globmatch('uploads/' + '_'*255, 'uploads/*_*_*_*_*.csv').
  4. Trigger CPU exhaustion: The wcmatch regex engine attempts all possible splits of the filename across the star segments, consuming tens of seconds of CPU per request. Repeated submissions can sustain a Denial of Service condition on the server (GitHub Advisory).

Indicateurs de compromis

  • Application Behavior: Sudden, sustained CPU spikes on the server process handling file matching or upload operations; requests to file-matching endpoints taking tens of seconds or timing out.
  • Logs: Application logs showing unusually long processing times for filename validation or glob operations; repeated requests with filenames consisting of long sequences of a single repeated character (e.g., underscores).
  • File System: Presence of files with names consisting of many repeated characters (e.g., 200–255 underscores) in directories scanned by wcmatch glob operations.
  • Network: High volume of requests to upload or file-filter endpoints, each with filenames near the maximum filesystem length and lacking expected file extensions (GitHub Advisory).

Atténuation et solutions de contournement

Upgrade wcmatch to version 11.2 or later, which fixes the vulnerability by wrapping each star segment except the last in an atomic group ((?>...)), preventing the regex engine from backtracking across star boundaries — the same approach used by CPython's own fnmatch fix (bpo-40480). Note that the fix requires Python 3.11 or later, as atomic groups are not available in Python 3.10; version 11.2 also drops support for Python 3.10. No configuration-based workaround is available for the default-flag code paths; the only remediation is upgrading the library (GitHub Advisory, Release 11.2, Fix Commit).

Réactions de la communauté

The vulnerability was discovered and reported by researcher @gistrec, who is credited in both the GitHub Security Advisory and the fix commit. The maintainer (facelessuser) promptly addressed the issue in version 11.2, adopting the same atomic-group approach used by CPython to fix an analogous backtracking problem in its standard library fnmatch (bpo-40480). No significant broader media coverage or social media discussion has been observed beyond the advisory itself (GitHub Advisory, Release 11.2).

Ressources supplémentaires

État de correction de la distribution Linux

Corrigez la disponibilité entre les grandes distributions Linux et leurs versions.

RHEL / CentOS

Inconnu

Source: Ce rapport a été généré à l’aide de l’IA

Connexe Python Vulnérabilités :

CVE ID

Gravité

Partition

Technologies

Nom du composant

Exploit CISA KEV

A corrigé

Date de publication

CVE-2026-132275HIGH7.5
  • Python logoPython
  • svglib
NonOuiNov 20, 2026
CVE-2026-132276MEDIUM5.9
  • Python logoPython
  • wcmatch
NonOuiNov 20, 2026
CVE-2026-132277MEDIUM5.3
  • Python logoPython
  • inscriptis
NonOuiNov 20, 2026
CVE-2026-77332LOW2.3
  • Python logoPython
  • memtomem-stm
NonOuiNov 20, 2026
CVE-2026-77331LOW2
  • Python logoPython
  • memtomem-stm
NonOuiNov 20, 2026

Évaluation gratuite des vulnérabilités

Évaluez votre posture de sécurité cloud

Évaluez vos pratiques de sécurité cloud dans 9 domaines de sécurité afin d’évaluer votre niveau de risque et d’identifier les lacunes dans vos défenses.

Évaluation de la demande

Ressources Wiz supplémentaires

Obtenez une démo personnalisée

Prêt(e) à voir Wiz en action ?

"La meilleure expérience utilisateur que j’ai jamais vue, offre une visibilité totale sur les workloads cloud."
David EstlickRSSI
"Wiz fournit une interface unique pour voir ce qui se passe dans nos environnements cloud."
Adam FletcherChef du service de sécurité
"Nous savons que si Wiz identifie quelque chose comme critique, c’est qu’il l’est réellement."
Greg PoniatowskiResponsable de la gestion des menaces et des vulnérabilités