CRLF vulnerability in Fiber
Published 29 Jun 2021 路 Updated 8 Jul 2026
Is your project on an affected github.com/gofiber/fiber?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <1.12.6
- Fixed in
- 1.12.6
go get github.com/gofiber/fiber@v1.12.6Details
Impact
The filename that is given in c.Attachment() is not escaped, and therefore vulnerable for a CRLF injection attack. I.e. an attacker could upload a custom filename and then give the link to the victim. With this filename, the attacker can change the name of the downloaded file, redirect to another site, change the authorization header, etc.
Steps to reproduce
package main
import "github.com/gofiber/fiber"
const badFileName = "another secret document.pdf\"\r\nLocation: google.com\r\nAuthorization: \"example_of_session_fixation"
func splitTheResponse(c *fiber.Ctx) {
c.Attachment(badFileName)
}
func main() {
app := fiber.New()
app.Get("/attack", splitTheResponse)
app.Listen("127.0.0.1:8080")
}HTTP/1.1 200 OK Date: Fri, 10 Jul 2020 19:47:04 GMT Content-Type: application/octet-stream Content-Length: 0 Content-Disposition: attachment; filename="another secret document.pdf" Location: google.com Authorization: "example_of_session_fixation"
Patches
This issue has been patched in v1.12.6 with commit 579 escaping the filename by default.
Workarounds
You could of course serialize the input yourself before passing it to ctx.Attachment(), this is actually a good practice by default. But in case you forget, we got you covered 馃憤
References
A CRLF injection attack is one of several types of injection attacks. It can be used to escalate to more malicious attacks such as Cross-site Scripting (XSS), page injection, web cache poisoning, cache-based defacement, and more. A CRLF injection vulnerability exists if an attacker can inject the CRLF characters into a web application, for example using a user input form or an HTTP request, see acunetix
For more information
If you have any questions or comments about this advisory:
- Open an issue in gofiber/fiber
- Join us on Discord
Is GHSA-9cx9-x2gp-9qvh in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/gofiber/fiber, and gives you the command that fixes it.
More advisories for github.com/gofiber/fiber
- MediumCVE-2026-53624GoFiber never set HSTS header in helmet middleware due to incorrect protocol check 路 6 Jul 2026
- LowCVE-2025-66630Fiber has an insecure fallback in utils.UUIDv4() / utils.UUID() on crypto/rand failure in github.com/gofiber/fiber 路 19 Feb 2026
- LowCVE-2025-48075Fiber panics when fiber.Ctx.BodyParser parses invalid range index in github.com/gofiber/fiber 路 27 May 2025
- LowCVE-2024-38513Session Middleware Token Injection Vulnerability in github.com/gofiber/fiber 路 2 Jul 2024
- CriticalCVE-2024-38513Session Middleware Token Injection Vulnerability 路 1 Jul 2024
- MediumCVE-2023-41338Fiber unauthorized access vulnerability in `ctx.IsFromLocal()` 路 8 Sept 2023
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.