At Black Hat and DEF CON 2025, PortSwigger researcher James Kettle presented new "desync" attacks under the banner HTTP/1.1 must die. His work uncovered a flaw at Cloudflare that exposed more than 24 million sites to takeover, and earned Akamai the identifier CVE-2025-32094. The research collected over $350,000 in bug bounty rewards.
What is going on
HTTP/1.1 is the older language that browsers, content delivery networks (CDNs) and web servers use to pass requests around. Most sites today sit behind a CDN or reverse proxy, a middle server that receives visitor traffic and forwards it to the real server, called the origin.
HTTP request smuggling happens when the middle server and the origin read the same stream of text differently. An attacker hides a second request inside the first. The middle server sees one request; the origin sees two.
Think of two clerks reading one letter and disagreeing about where it ends. The leftover text gets stuck to the next person's letter. In web terms, the attacker's hidden request attaches to the next visitor's traffic, which can lead to stolen sessions or full site takeover.
Who is affected
The risk sits with websites behind CDNs and reverse proxies that still speak HTTP/1.1 to their origin server. That covers a very large share of ordinary business sites, including shops and brochure sites on shared hosting.
The specific issues named in the research affected Cloudflare and Akamai, with CVE-2025-32094 assigned to the Akamai flaw. These are provider-side problems, so the fixes mostly happen above your hosting account rather than inside your CMS.
What to do now
- Ask your CDN or host to use HTTP/2 between the proxy and your origin server where it is supported. This removes the ambiguity that desync attacks rely on.
- Enable request normalization at your CDN or proxy, so odd or conflicting requests are cleaned up before they reach your origin.
- Confirm with your provider that they have applied the fixes from this research.
- If you have a developer or agency, ask them to test your setup with PortSwigger's HTTP Request Smuggler tool.
- Keep your CMS, plugins and server software updated, so a smuggled request has fewer things to abuse.
How to check your own site
Request smuggling itself is tested at the proxy layer, but the rest of your exposure is easy to review. The free Website Security Check from Scantinel flags outdated CMS versions, known-vulnerable plugins, missing security headers, weak TLS and email-authentication gaps. If you have verified ownership of the site, you can also run a full scan, which adds active OWASP Top 10 testing, port and service checks with CVE matching, WordPress and Magento deep scans, and exposed-file and secret checks.
Source: portswigger.net/research/http1-must-die, August 2025.
Comments
No comments yet.