aiohttp allows unlimited trailer headers, leading to possible uncapped memory usage
Published Apr 1, 2026 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
aiohttp allows unlimited trailer headers, leading to possible uncapped memory usage
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
Insufficient restrictions in header/trailer handling could cause uncapped memory usage.
Potential impact
An application could cause memory exhaustion when receiving an attacker controlled request or response. A vulnerable web application could mitigate these risks with a typical reverse proxy configuration. ----- Patch: https://github.com/aio-libs/aiohttp/commit/0c2e9da51126238a421568eb7c5b53e5b5d17b36
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- MEDIUM
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
Record history
Published Apr 1, 2026 · Last refreshed Nov 3, 2026