This weekExploitable · Confirmed
llhttp: llhttp allows HTTP Request Smuggling via Improper Delimiting of Header Fields
There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.
Does it affect what I run?
llhttp (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- llhttp (npm): every version, before 6.0.7
The fix
llhttp (npm) fixed in 6.0.7
npmnpm install llhttp@6.0.7pnpmpnpm add llhttp@6.0.7yarnyarn add llhttp@6.0.7bunbun add llhttp@6.0.7Check what is installednpm ls llhttpPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency llhttp to 6.0.7 or the nearest later release, to fix CVE-2022-32214. 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
EPSS puts the chance of exploitation in the next 30 days at 82%.
FIRST EPSSStated
Timeline
- First published here, as "For your digest".
- Level changed from "For your digest" to "This week".
- Evidence added: EPSS rates exploitation in the next 30 days as more likely than not. (FIRST EPSS)