AIOHTTP: Pure-Python parser request smuggling

Exploitation

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

CVSS 4.0

6.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:L/SA:L · score source

EPSS

• CVE-2026-111750: 0.38% estimated exploitation activity in the next 30 days; percentile 32.23 (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 The pure Python parser is vulnerable to an HTTP request smuggling attack. Impact If users are using the Python parser (AIOHTTPNOEXTENSIONS, or not a standard wheel installed), then an application may be vulnerable to a request smuggling attack. Workaround Switch to the default C parser.

Published by the source

20 Oct 2026, 19:52 UTC

Last modified by the source

20 Oct 2026, 20:00 UTC

Source last checked

26 Oct 2026, 13:55 UTC

1. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-pqxq-w44r-73xw

2. Revision 3 · amended · 25 Oct 2026

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

3. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-pqxq-w44r-73xw

4. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-pqxq-w44r-73xw

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

# Patch Next advisory brief: CVE-2026-111750

Advisory: AIOHTTP: Pure-Python parser request smuggling
IDs: CVE-2026-111750, GHSA-pqxq-w44r-73xw
Record: https://patchnext.com/advisories/cve-2026-111750 (revision 4, source checked 26 Oct 2026, 13:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
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.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI aiohttp: affected <= 3.14.3; fixed in 3.14.4

## 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://github.com/advisories/GHSA-pqxq-w44r-73xw (GitHub-reviewed advisory GHSA-pqxq-w44r-73xw lists affected ranges: PyPI aiohttp >=0 <=3.14.3)
- Verified: https://osv.dev/vulnerability/GHSA-pqxq-w44r-73xw (OSV record GHSA-pqxq-w44r-73xw lists affected ranges: PyPI aiohttp >=0 <3.14.4 (fixed))

Commands are suggestions: review each one before running it.