An issue was discovered in the async-h1 crate before 2.3.0 for Rust.
Priority LOW 29CWE-79Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Cross-site scripting
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA and GitHub. Impact type from CWE-79.
Summary
An issue was discovered in the async-h1 crate before 2.3.0 for Rust. Request smuggling can occur when used behind a reverse proxy.
Why it matters now
EPSS 0.00825 57th percentileScored 2026-11-07
Fix Fixed async-h1 (crates.io): 2.3.0
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | — | all versions | — | No fix listed | CNA |
| — | async-h1 (crates.io) | before 2.3.0 | 2.3.0 | Patch available | GHSA-c8rq-crxj-mj9m |
- — Vendor— Affected all versions Fixed in — No fix listed CNA
- async-h1 (crates.io) Vendor— Affected before 2.3.0 Fixed in 2.3.0 Patch available GHSA-c8rq-crxj-mj9m
Remediation
- Fix · GHSA-c8rq-crxj-mj9m async-h1 (crates.io) Fixed in 2.3.0 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2020-36202
- 2026-10-03 Alias added: GHSA-c8rq-crxj-mj9m
References
More rust-lang Async-h1 vulnerabilities
- TI-2020-16102 request smuggling in async-h1 CVSS 3.1HIGH 7.5
Sources
- CVE-2020-36202 · CVE Program
- CVE-2020-36202 · NVD
- FIRST EPSS
- GHSA-c8rq-crxj-mj9m · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences