ASR AI Security Radar

Back to incidents

AI security incident: minimatch has a ReDoS via repeated wildcards with non-matching literal in pattern (GH...

Incident date: February 18, 2026 | Published: February 25, 2026 | Source: GitHub Security Advisory | Classification confidence: 45%

This incident is part of the public archive. AI-specific signals are limited in the current source material, so source citations should be reviewed closely during triage. Review methodology.

Summary minimatch is vulnerable to Regular Expression Denial of Service (ReDoS) when a glob pattern contains many consecutive * wildcards followed by a literal character that doesn't appear in the test string. Each * compiles to a separate [^/]*? regex group, and when the match fails, V8's regex engine backtracks exponentially across all possible splits. The time complexity is O(4^N) where N is the number of * characters. With N=15, a single minimatch() call takes ~2 seconds. With N=34, it hangs effectively forever. ### Details _Give all details on the vulnerability. Pointing to the incriminated source code is very helpful for the maintainer._ ### PoC When minimatch compiles a glob pattern, each * becomes [^/]*? in the generated regex.

Why This Is AI-Related

This advisory is part of the public incident archive, but the current source material uses limited explicit AI terminology, so the cited sources should be reviewed carefully when judging AI relevance and exposure.

  • Explicit AI-specific signals are limited in the current source material, so use the cited advisory to validate scope during triage.

Affected Workflow

Check inference endpoints, parsing layers, queues, and file processing jobs that support AI features.

Likely Attack Path

An attacker can drive resource exhaustion or crash conditions in the vulnerable component through crafted traffic or content.

Impact

The advisory describes an availability or resource-exhaustion path that can disrupt AI-serving components and supporting automation. Severity HIGH. Classification confidence 45%. Source channel GHSA.

Detection And Triage Signals

  • Latency spikes or worker restarts on AI-serving endpoints
  • Memory or CPU saturation after malformed requests or artifacts
  • Queue backlogs, timeouts, or repeated crash loops in model services

Recommended Response

  • Identify inference endpoints, parsing jobs, or queues that rely on the affected component.
  • Apply vendor mitigations and add rate, size, or input controls to reduce exhaustion risk during triage.
  • Monitor latency, restart frequency, queue backlog, and saturation indicators for active disruption.

Compliance And Business Impact

Availability failures can interrupt customer-facing AI features and force emergency rollback or capacity isolation.

Sources

Want alerts like this in real time?

Get notified with incident context, likely impact, and response guidance.

Get Notified

More incidents