{"id":"CVE-2026-15157","aliases":["GHSA-m8rv-5g2x-5cg5"],"title":"undici vulnerable to CRLF Injection via blob-like body 'type' property","summary":"undici vulnerable to CRLF Injection via blob-like body 'type' property","severity":"medium","cvss":4.2,"cwe":["CWE-93"],"vendor":"undici","product":"undici","ecosystem":"npm","affected":["undici < 6.28.0","undici >= 7.0.0, < 7.29.0","undici >= 8.0.0, < 8.9.0"],"patched":["undici 6.28.0","undici 7.29.0","undici 8.9.0"],"published":"2026-08-03","updated":"2026-08-03","source":"GHSA","sourceUrl":"https://github.com/advisories/GHSA-m8rv-5g2x-5cg5","references":[{"url":"https://github.com/nodejs/undici/security/advisories/GHSA-m8rv-5g2x-5cg5"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-15157"},{"url":"https://github.com/nodejs/undici/commit/33928bc24f742ea8422ed90d17f2e0cc83e4d09d"},{"url":"https://github.com/nodejs/undici/commit/740a0b7c173cb4a83a5b693e96e8f3a116cfc400"},{"url":"https://github.com/nodejs/undici/commit/7d3cf924c262c486bc77f951348f4e5c847b7b42"},{"url":"https://cna.openjsf.org/security-advisories.html"},{"url":"https://github.com/nodejs/undici/releases/tag/v6.28.0"},{"url":"https://github.com/nodejs/undici/releases/tag/v7.29.0"},{"url":"https://github.com/nodejs/undici/releases/tag/v8.9.0"},{"url":"https://github.com/advisories/GHSA-m8rv-5g2x-5cg5"}],"tags":["ghsa","npm"],"epss":0.00193,"epssPercentile":0.09211,"ingestedAt":"2026-08-03T20:29:32.447Z","slug":"CVE-2026-15157","body":"## Overview\n\n### Impact\n\nWhen an application passes a duck-typed blob-like body to undici's HTTP/1.1 dispatcher (via `request()`, `stream()`, `pipeline()`, or `dispatch()`) with a `.type` derived from untrusted input, an attacker can inject CRLF sequences (`\\r\\n`) to append arbitrary HTTP headers and potentially smuggle a second request past the upstream.\n\nThe vulnerable branch in `lib/dispatcher/client-h1.js` pushes `body.type` directly into the outgoing headers with no validation, while every other header path in undici goes through `isValidHeaderValue()`:\n\n```javascript\n} else if (util.isBlobLike(body) && request.contentType == null && body.type) {\n  headers.push('content-type', body.type)  // bypasses isValidHeaderValue()\n}\n```\n\nThe bug requires a hand-rolled duck-typed blob object or a Blob subclass with a controlled `.type`. Native `Blob` is safe because its constructor strips CRLF from `.type`. `fetch()` is unaffected because it validates via the `Headers` class. Ecosystem consumers that build duck-typed blob shapes from user input include `form-data-encoder`, `formdata-polyfill`, and `formdata-node`.\n\nSame defect class as `CVE-2022-35948` (explicit `content-type` sink, fixed in undici 5.8.2) and `CVE-2026-1527` (`upgrade` option sink, fixed in 6.24.0 / 7.24.0), both closed by adding `isValidHeaderValue()` on their respective sinks. This branch was missed.\n\n### Patches\n\nPatched in undici v6.28.0, v7.29.0, and v8.9.0. Users should upgrade to one of these versions or later.\n\n### Workarounds\n\n- Set an explicit, validated `content-type` header on the request options (skips the vulnerable branch).\n- Use a native `Blob` (or `fetch-blob`) instead of a hand-rolled duck-typed object.\n- Reject control characters in the MIME type before assigning it to `.type`.\n- Use `fetch()` instead of the non-`fetch` APIs.\n\n## Affected packages\n\n- `undici < 6.28.0`\n- `undici >= 7.0.0, < 7.29.0`\n- `undici >= 8.0.0, < 8.9.0`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `undici 6.28.0`\n- `undici 7.29.0`\n- `undici 8.9.0`","depth":"sunlit","depthScore":23,"depthScoreParts":{"impact":23.1,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}