CVE-2026-74866: @fastify/busboy vulnerable to CRLF injection via multipart Content-Disposition filename and name
@fastify/busboy 3.2.1 and earlier retains a bare carriage return or line feed inside the parsed Content-Disposition parameters returned to the application. The multipart header parser ends a header line only on the two-byte \r\n sequence, so a lone CR or LF embedded in a part header is carried verbatim into the filename and field name delivered by the file and field events. An application that forwards the supplied filename or name into a CR/LF-sensitive sink cannot anticipate the embedded control character.
An attacker who uploads a file whose filename or field name contains a bare CR or LF can pollute filenames on disk when the upload is saved under its original name, inject forged lines into logs, or inject headers on a downstream hop that does not re-validate CR/LF, such as object-storage metadata or a proxied backend. Applications using @fastify/busboy directly, or through @fastify/multipart and its consumers, are affected.
References
- cna.openjsf.org/security-advisories.html
- github.com/advisories/GHSA-gxm5-99cw-xjw9
- github.com/fastify/busboy/commit/cc7da17c5c88d79c314a9e149a79e5a00a6c23be
- github.com/fastify/busboy/releases/tag/v3.2.2
- github.com/fastify/busboy/security/advisories/GHSA-gxm5-99cw-xjw9
- nvd.nist.gov/vuln/detail/CVE-2026-74866
Code Behaviors & Features
Detect and mitigate CVE-2026-74866 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →