CVE-2026-85077
Sanic vulnerability
- Published17 Sept 2026
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:NRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://github.com/sanic-org/sanic/commit/47349d689d65fa1907977ac100e867894aeafb22
- https://github.com/sanic-org/sanic/commit/9a95bb1c187558949606b915f5162c15f2db781b
- https://github.com/sanic-org/sanic/commit/a332796506c7c588b6930b02a8886e43eb8ea8d6
- https://github.com/sanic-org/sanic/pull/3164
- https://github.com/sanic-org/sanic/pull/3165
- https://github.com/sanic-org/sanic/releases/tag/v24.12.1
- https://github.com/sanic-org/sanic/releases/tag/v25.12.1
- https://github.com/sanic-org/sanic/security/advisories/GHSA-m64h-22vf-48wm
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-85077 being actively exploited?
CVE-2026-85077 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.48%.
How severe is CVE-2026-85077?
CVE-2026-85077 has a CVSS 3.1 base score of 8.2, rated high. EPSS estimates a 0.48% probability of exploitation.
How do I fix CVE-2026-85077?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-85077 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.