Skip to main content
VulnerabilityPublished Updated

CVE-2024-6827: benoitc/gunicorn · Inconsistent Interpretation of HTTP Requests

Affects benoitc/gunicornSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.0 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Mar 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
PyPIgunicornpkg:pypi/gunicornOther threatsAffected
  • =21.2.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediate mitigation should focus on upgrading Gunicorn to a version that properly validates the 'Transfer-Encoding' header and eliminates the fallback to 'Content-Length' parsing. Until a patch is available, organizations should implement strict input validation and filtering at the perimeter, such as configuring web application firewalls (WAFs) to detect and block malformed or suspicious 'Transfer-Encoding' headers. Reverse proxies like Nginx or Apache should be configured to reject ambiguous or conflicting HTTP headers. Network segmentation can limit the impact of SSRF and lateral movement. Monitoring and logging HTTP request anomalies can help detect exploitation attempts early. Additionally, reviewing and hardening caching mechanisms to prevent poisoning and ensuring secure session management practices will reduce risk. Organizations should also conduct penetration testing focused on HTTP request smuggling to identify vulnerable endpoints. Finally, maintaining an incident response plan tailored to web application attacks will improve readiness.

Description

Gunicorn version 21.2.0 does not properly validate the value of the 'Transfer-Encoding' header as specified in the RFC standards, which leads to the default fallback method of 'Content-Length,' making it vulnerable to TE.CL request smuggling. This vulnerability can lead to cache poisoning, data exposure, session manipulation, SSRF, XSS, DoS, data integrity compromise, security bypass, information leakage, and business logic abuse.

References

Community reviews

Loading reviews…