This weekExploitable · Confirmed
brace-expansion: brace-expansion Regular Expression Denial of Service vulnerability
There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.
Does it affect what I run?
brace-expansion (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- brace-expansion (npm): from 2.0.0, before 2.0.2
- brace-expansion (npm): from 1.0.0, before 1.1.12
- brace-expansion (npm): from 3.0.0, before 3.0.1
- brace-expansion (npm): from 4.0.0, before 4.0.1
The fix
brace-expansion (npm) fixed in 2.0.2
npmnpm install brace-expansion@2.0.2pnpmpnpm add brace-expansion@2.0.2yarnyarn add brace-expansion@2.0.2bunbun add brace-expansion@2.0.2Check what is installednpm ls brace-expansionPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency brace-expansion to 2.0.2 or the nearest later release, to fix CVE-2025-5889. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.brace-expansion (npm) fixed in 1.1.12
npmnpm install brace-expansion@1.1.12pnpmpnpm add brace-expansion@1.1.12yarnyarn add brace-expansion@1.1.12bunbun add brace-expansion@1.1.12Check what is installednpm ls brace-expansionPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency brace-expansion to 1.1.12 or the nearest later release, to fix CVE-2025-5889. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.brace-expansion (npm) fixed in 3.0.1
npmnpm install brace-expansion@3.0.1pnpmpnpm add brace-expansion@3.0.1yarnyarn add brace-expansion@3.0.1bunbun add brace-expansion@3.0.1Check what is installednpm ls brace-expansionPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency brace-expansion to 3.0.1 or the nearest later release, to fix CVE-2025-5889. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.brace-expansion (npm) fixed in 4.0.1
npmnpm install brace-expansion@4.0.1pnpmpnpm add brace-expansion@4.0.1yarnyarn add brace-expansion@4.0.1bunbun add brace-expansion@4.0.1Check what is installednpm ls brace-expansionPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency brace-expansion to 4.0.1 or the nearest later release, to fix CVE-2025-5889. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
Exploitable · Confirmed
CISA's assessment in the CVE record says a proof of concept is public.
CISA Vulnrichment (SSVC and KEV fields inside CVE records)Stated
Timeline
- First published here, as "For your digest".
- Level changed from "For your digest" to "This week".
- Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))