# In aiohttp, compressed files as symlinks are not protected from path traversal

Advisory record · `GHSA-jwhx-xcg6-8xhj`

- **Identifiers:** `GHSA-jwhx-xcg6-8xhj` · `CVE-2024-42367` · `PYSEC-2026-1108`
- **State:** Confirmed
- **Severity:** CVSS 4.8 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-61](https://cwe.mitre.org/data/definitions/61.html)
- **Tags:** [CWE-61](https://agentprime.io/advisories/tag/cwe-61.md)
- **Published:** 9 Aug 2024
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 9 Aug 2024, 16:49 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `aiohttp` (PyPI): affected `>=3.10.0b1, <3.10.2`; fixed in `3.10.2`

## Machine-written summary

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

> Affected versions of aiohttp from 3.10.0b1 up to but not including 3.10.2 are vulnerable to path traversal through static routes. If a static route's files have compressed variants (.gz or .br) that are symbolic links pointing outside the root directory, a remote user can request them and read files outside that directory. Upgrade to aiohttp 3.10.2 or later. The source gives no workaround.

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

- 4.8 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0065, the 51st percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:35 UTC: First seen by agentprime
- 31 Oct 2026, 14:35 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jwhx-xcg6-8xhj)

## Sources

- [GitHub Advisory Database: GHSA-jwhx-xcg6-8xhj](https://github.com/advisories/GHSA-jwhx-xcg6-8xhj)
- [OSV: GHSA-jwhx-xcg6-8xhj](https://osv.dev/vulnerability/GHSA-jwhx-xcg6-8xhj)
- <https://github.com/aio-libs/aiohttp/security/advisories/GHSA-jwhx-xcg6-8xhj>
- <https://nvd.nist.gov/vuln/detail/CVE-2024-42367>
- <https://github.com/aio-libs/aiohttp/pull/8653>
- <https://github.com/aio-libs/aiohttp/commit/ce2e9758814527589b10759a20783fb03b98339f>
- <https://github.com/aio-libs/aiohttp>
- <https://github.com/aio-libs/aiohttp/blob/e0ff5246e1d29b7710ab1a2bbc972b48169f1c05/aiohttp/web_fileresponse.py#L177>
- <https://github.com/aio-libs/aiohttp/blob/e0ff5246e1d29b7710ab1a2bbc972b48169f1c05/aiohttp/web_urldispatcher.py#L674>

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-jwhx-xcg6-8xhj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jwhx-xcg6-8xhj/>. Everything for agents: <https://agentprime.io/llms.txt>.