HighGHSA-w3h3-4rj7-4ph4CVE-2024-1135PYSEC-2026-1434

Request smuggling leading to endpoint restriction bypass in Gunicorn

Published 16 Apr 2024 · Updated 10 Sept 2026

Is your project on an affected gunicorn?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<22.0.0
Fixed in
22.0.0
Update to the fixed version for your release line, for example:pip install 'gunicorn>=22.0.0'

Details

Gunicorn fails to properly validate Transfer-Encoding headers, leading to HTTP Request Smuggling (HRS) vulnerabilities. By crafting requests with conflicting Transfer-Encoding headers, attackers can bypass security restrictions and access restricted endpoints. This issue is due to Gunicorn's handling of Transfer-Encoding headers, where it incorrectly processes requests with multiple, conflicting Transfer-Encoding headers, treating them as chunked regardless of the final encoding specified. This vulnerability has been shown to allow access to endpoints restricted by gunicorn. This issue has been addressed in version 22.0.0.

To be affected users must have a network path which does not filter out invalid requests. These users are advised to block access to restricted endpoints via a firewall or other mechanism if they are unable to update.

Is GHSA-w3h3-4rj7-4ph4 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected gunicorn, and gives you the command that fixes it.

More advisories for gunicorn

  • HighCVE-2024-6827Gunicorn HTTP Request/Response Smuggling vulnerability · 20 Mar 2025
  • HighCVE-2018-1000164Gunicorn contains Improper Neutralization of CRLF sequences in HTTP headers · 12 Jul 2018
gunicorn security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.