Web & network
HTTP request smuggling
HTTP request desynchronisation, request smuggling
Differences in HTTP message parsing between a front-end proxy and a back-end server can allow injected requests to cross request boundaries.
Fiche de sensibilisationPrête à diffuser à vos équipes ou clients
MIGHT YOU BE AFFECTED?
Turn knowledge into action.
How does this work?
If two HTTP components disagree on where one request ends—for example because they handle message length or transfer encoding differently—an attacker may cause subsequent bytes to be interpreted as another request.
REAL-WORLD EXAMPLE
« A malformed request passes through a reverse proxy and causes a hidden back-end request to be associated with another user's connection, potentially contaminating a cached response. »
Typical sequence
- 1The attacker identifies inconsistent parsing between the proxy and origin.
- 2They submit an ambiguously framed request.
- 3Front-end and back-end components disagree on request boundaries.
- 4A hidden request may be processed or responses may be associated with the wrong client.
Warning signs
- Intermittent mismatched responses or unusual 400 errors.
- Conflicting or duplicated HTTP framing headers.
- Unexpected back-end requests not matching front-end access logs.
- Cache entries or sessions showing cross-user contamination.
How to protect yourself
- Reject ambiguous requests and normalise HTTP framing at the edge.
- Patch and align proxy, load balancer and origin-server HTTP parsing.
- Prefer end-to-end consistent HTTP protocol handling and disable unsafe downgrades.
- Monitor anomalous framing errors and test reverse-proxy chains safely.
If you think you are affected
Restrict the affected traffic path, preserve proxy and origin logs and investigate cross-user impact. Update all affected HTTP components, verify consistent parsing and invalidate any contaminated cache or sessions.
Last updated: 8 October 2026