# aiohttp has vulnerable dependency that is vulnerable to request smuggling

Advisory record · `GHSA-pjjw-qhg8-p2p9`

- **Identifiers:** `GHSA-pjjw-qhg8-p2p9`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-444](https://cwe.mitre.org/data/definitions/444.html)
- **Tags:** [HTTP request smuggling](https://agentprime.io/advisories/tag/request-smuggling.md)
- **Published:** 27 Nov 2023
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 27 Nov 2023, 23:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `aiohttp` (PyPI): affected `<3.8.6`; fixed in `3.8.6`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> aiohttp versions before 3.8.6 are affected because they bundle llhttp 8.1.1, which has two request smuggling vulnerabilities. The source gives few details and says the specifics have not been disclosed. Upgrade aiohttp to 3.8.6 or later, which uses llhttp 9 or newer; no workaround is listed.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:36 UTC: First seen by agentprime
- 31 Oct 2026, 14:36 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-pjjw-qhg8-p2p9)

## Sources

- [GitHub Advisory Database: GHSA-pjjw-qhg8-p2p9](https://github.com/advisories/GHSA-pjjw-qhg8-p2p9)
- [OSV: GHSA-pjjw-qhg8-p2p9](https://osv.dev/vulnerability/GHSA-pjjw-qhg8-p2p9)
- <https://github.com/aio-libs/aiohttp/security/advisories/GHSA-pjjw-qhg8-p2p9>
- <https://github.com/aio-libs/aiohttp/commit/996de2629ef6b4c2934a7c04dfd49d0950d4c43b>
- <https://github.com/aio-libs/aiohttp/commit/bcc416e533796d04fb8124ef1e7686b1f338767a>
- <https://github.com/aio-libs/aiohttp>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-pjjw-qhg8-p2p9>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-pjjw-qhg8-p2p9/>. Everything for agents: <https://agentprime.io/llms.txt>.