CVE-2026-85077
HighCVSS 8.2Summary
Sanic is an opensource python web server/framework. Prior to version 24.12.1, and in version 25.12.0, the HTTP/1.1 response pipeline in sanic/response/types.py serializes response header names and values without rejecting carriage-return or line-feed characters. Applications that place attacker-controlled data in response.headers, file(..., filename=...), or cookie path and domain attributes can therefore emit injected headers and may split responses. Depending on application and proxy behavior, this can enable session fixation through injected cookies, cache poisoning, or security-header corruption. This issue is fixed in versions 24.12.1 and 25.12.1.
Risk Assessment
Possible header injection and response splitting, leading to session fixation, cache poisoning, or weakened security headers.
Recommendation
Update Sanic to version 24.12.1 or 25.12.1 and avoid placing untrusted data in response headers and cookie attributes.
Other vulnerabilities in Sanic
See all- CVE-2026-85078Medium
In Sanic version 25.12.0, HTTP/1.1 chunked-body handling does not fully consume the trailer-part after the terminating zero chunk before reusing the keep-alive connection buffer. A remote unauthenticated client can place attacker-controlled bytes in that trailer region, which Sanic parses and routes as a hidden second request. This breaks HTTP request-boundary integrity and can provide a request-smuggling primitive when Sanic is deployed behind intermediaries.
- CVE-2017-16762High
Sanic versions before 0.5.1 allow reading arbitrary files through directory traversal, as demonstrated by the /static/..%2f substring.
Original NVD description (English source)
Sanic is an opensource python web server/framework. Prior to version 24.12.1, and in version 25.12.0, the HTTP/1.1 response pipeline in sanic/response/types.py serializes response header names and values without rejecting carriage-return or line-feed characters. Applications that place attacker-controlled data in response.headers, file(..., filename=...), or cookie path and domain attributes can therefore emit injected headers and may split responses. Depending on application and proxy behavior, this can enable session fixation through injected cookies, cache poisoning, or security-header corruption. This issue is fixed in versions 24.12.1 and 25.12.1.