Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Gunicorn versions before 22.0.0 do not properly validate the Transfer-Encoding header, so requests can be handled using Content-Length instead, enabling TE.CL request smuggling. An attacker who can send HTTP requests through a proxy or front-end in front of Gunicorn could smuggle requests, which may enable cache poisoning, session manipulation, or security bypass. Upgrade to gunicorn 22.0.0 or later. The source gives few details on specific exploitation conditions.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.0 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | CNA (@huntr_ai) |
- CISA KEV Not listed.
- EPSS 0.0081, the 56th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:37 UTC First seen by agentprime
- 31 Oct 2026, 14:37 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-hc5x-x2vx-497g
- OSV: GHSA-hc5x-x2vx-497g
- nvd.nist.gov/vuln/detail/CVE-2024-6827
- github.com/benoitc/gunicorn/issues/3087
- github.com/benoitc/gunicorn/issues/3278
- github.com/benoitc/gunicorn/pull/3113
- github.com/benoitc/gunicorn
- github.com/benoitc/gunicorn/releases/tag/22.0.0
- huntr.com/bounties/1b4f8f38-39da-44b6-9f98-f618639d0dd7