aiohttp: Unread Compressed Request Bodies Bypass client_max_size During Cleanup

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.6 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U · score source

EPSS

• CVE-2026-54278: 0.49% estimated exploitation activity in the next 30 days; percentile 42.42 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary During cleanup it is possible for a compressed request body to be decompressed into memory in one chunk. Impact An attacker may be able to send a compressed payload in specific situations that could be decompressed into memory, potentially leading to DoS (a zip bomb edge case). Workaround Disable compression if unable to upgrade. ----- Patch: https://github.com/aio-libs/aiohttp/commit/4f7480e474cccc6a8cc2c92ad3f17a31dedf8232

Published by the source

15 Jun 2026, 20:09 UTC

Last modified by the source

10 Sep 2026, 03:51 UTC

Source last checked

26 Oct 2026, 13:45 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-g3cq-j2xw-wf74

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-g3cq-j2xw-wf74

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54278

Advisory: aiohttp: Unread Compressed Request Bodies Bypass client_max_size During Cleanup
IDs: CVE-2026-54278, GHSA-g3cq-j2xw-wf74
Record: https://patchnext.com/advisories/cve-2026-54278 (revision 3, source checked 26 Oct 2026, 13:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: aiohttp 3.14.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI aiohttp: affected <= 3.14.0; fixed in 3.14.1

## Suggested inspection (read-only)
- `python -m pip show aiohttp`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on aiohttp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-g3cq-j2xw-wf74 (OSV record GHSA-g3cq-j2xw-wf74 lists affected ranges: PyPI aiohttp >=0 <3.14.1 (fixed))
- Verified: https://github.com/advisories/GHSA-g3cq-j2xw-wf74 (GitHub-reviewed advisory GHSA-g3cq-j2xw-wf74 lists affected ranges: PyPI aiohttp >=0 <=3.14.0)

Commands are suggestions: review each one before running it.