GHSA-v6h2-p8h4-qcjw is a low-severity (CVSS 3.1) Uncontrolled Resource Consumption vulnerability in brace-expansion. O3 Security confirms whether GHSA-v6h2-p8h4-qcjw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
brace-expansion Regular Expression Denial of Service vulnerability
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
brace-expansionnpmDescription
A vulnerability was found in juliangruber brace-expansion up to 1.1.11/2.0.1/3.0.0/4.0.0. It has been rated as problematic. Affected by this issue is the function expand of the file index.js. The manipulation leads to inefficient regular expression complexity. The attack may be launched remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. Upgrading to version 1.1.12, 2.0.2, 3.0.1 and 4.0.1 is able to address this issue. The name of the patch is a5b98a4f30d7813266b221435e1eaaf25a1b0ac5. It is recommended to upgrade the affected component.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | brace-expansion | ≥ 2.0.0&&< 2.0.2 | 2.0.2 |
| 📦npm | brace-expansion | ≥ 1.0.0&&< 1.1.12 | 1.1.12 |
| 📦npm | brace-expansion | ≥ 3.0.0&&< 3.0.1 | 3.0.1 |
| 📦npm | brace-expansion | ≥ 4.0.0&&< 4.0.1 | 4.0.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for brace-expansion. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update brace-expansion to 2.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v6h2-p8h4-qcjw is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-v6h2-p8h4-qcjw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-v6h2-p8h4-qcjw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-v6h2-p8h4-qcjw in your dependencies?
O3 detects GHSA-v6h2-p8h4-qcjw across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.