← Back to results
Vulnerability record · public intelligence
CVE-2026-85077
HIGH

Sanic: HTTP response header injection via missing CR/LF validation in Sanic HTTP/1.1 responses

Published Sep 17, 2026 · Updated Nov 3, 2026

Severity · CVSSHIGH · Not scored
Known exploitationNot listed
EPSS / likelihood0.48%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Nov 3, 2026

Sanic: HTTP response header injection via missing CR/LF validation in Sanic HTTP/1.1 responses

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

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.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

FIRST-EPSSCVE-LIST-V5
SSVC priority
MEDIUM
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Source repository ↗
  3. Source repository ↗
  4. Patch commit ↗
  5. Patch commit ↗
  6. Patch commit ↗
  7. Source repository ↗
  8. Source repository ↗

Record history

Published Sep 17, 2026 · Last refreshed Nov 3, 2026