---
id: 5507
title: "[CVE-2019-16276] HTTP Desync Attacks: what happened next"
cve: CVE-2019-16276
source_domain: portswigger.net
source_url: "https://portswigger.net/research/http-desync-attacks-what-happened-next"
published_at: "2022-09-20T08:04:00Z"
tags: ["http-desync", "request-smuggling", "vulnerability", "portswigger", "f5", "akamai", "cve-2019-16276"]
phying_url: "https://phying.com/item/5507"
lang: en
---

# [CVE-2019-16276] HTTP Desync Attacks: what happened next

## Summary

James Kettle follows up on HTTP Desync Attacks with vendor patches from Akamai, F5, HAProxy and Go's CVE-2019-16276, plus fresh desync techniques that expose more systems.

## Intelligence Metadata

- **Sources:** portswigger.net
- **CVE:** CVE-2019-16276
- **Published:** 2022-09-20T08:04:00Z
- **Original:** https://portswigger.net/research/http-desync-attacks-what-happened-next
- **Phying News:** https://phying.com/item/5507