AI security incident: qs's arrayLimit bypass in comma parsing allows denial of service (GHSA-w7fw-mjwx-w883)
Summary The arrayLimit option in qs does not enforce limits for comma-separated values when comma: true is enabled, allowing attackers to cause denial-of-service via memory exhaustion. This is a bypass of the array limit enforcement, similar to the bracket notation bypass addressed in GHSA-6rw7-vpxm-498p (CVE-2025-15284). ### Details When the comma option is set to true (not the default, but configurable in applications), qs allows parsing comma-separated strings as arrays (e.g., ?param=a,b,c becomes ['a', 'b', 'c'] ). However, the limit check for arrayLimit (default: 20) and the optional throwOnLimitExceeded occur after the comma-handling logic in parseArrayValue , enabling a bypass.
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