Skip to main content
VulnerabilityPublished Updated

CVE-2025-43859: Fastapi · h11 accepts some malformed Chunked-Encoding bodies

Affects fastapiSource GCVE Database

0

Not known to be exploited · CVSS 9.1 Critical : upgrade to 0.115.12_1 as a priority.

Data as of 27 Oct 2026, 23:14 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.115.12_1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  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

Upgrade fastapi to 0.115.12_1.

Affected software

ProductAffectedFixed in
Homebrewfastapipkg:brew/fastapiOther threatsAffected
  • >=0.111.0 <0.115.12_1
Fixed in
  • 0.115.12_1

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

AI-suggested

Upgrade h11 to version 0.15.0 or later to resolve the parsing issue. Alternatively, fix or replace any buggy reverse proxy that mishandles chunked encoding. Since exploitation requires both components to be vulnerable, remediating either the server-side h11 or the proxy suffices to mitigate the risk.

Description

A vulnerability in h11 versions up to 0.14.0 used by FastAPI allows malformed HTTP/1.1 chunked-encoding bodies to be accepted due to improper validation of trailing line terminators. This leniency can lead to HTTP request smuggling when combined with a buggy reverse proxy that parses chunked bodies differently. The issue is fixed in h11 version 0.15.0.

References

Community reviews

Loading reviews…