# StaticFile.fromUrl can leak presence of a directory

Advisory record · `GHSA-6h7w-fc84-x7p6`

- **Identifiers:** `GHSA-6h7w-fc84-x7p6` · `CVE-2021-32643`
- **State:** Confirmed
- **Severity:** CVSS 5.8 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 28 May 2021
- **Updated:** 8 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 28 May 2021, 15:54 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.http4s:http4s-core` (Maven): affected `>=0.21.7, <0.21.24 || >=0.22.0-M1, <0.22.0-RC1 || >=0.23.0-M1, <0.23.0-RC1 || >=1.0.0-M1, <1.0.0-M23`; fixed in `0.21.24`, `0.22.0-RC1`, `0.23.0-RC1`, `1.0.0-M23`

## Machine-written summary

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

> Versions of http4s-core from 0.21.7 up to 0.21.24 (excluding 0.21.24), and certain 0.22, 0.23 and 1.0 milestone builds, are affected. In StaticFile.fromUrl, a non-file URL pointing to a directory returns no resource without checking the scheme, so a remote attacker can infer whether a directory exists on the server from a 404 response. Upgrade to 0.21.24, 0.22.0-RC1, 0.23.0-RC1, 1.0.0-M23 or later. Avoid calling StaticFile.fromUrl with non-file URLs as a workaround.

Written 2 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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.014, the 72nd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:20 UTC: First seen by agentprime
- 31 Oct 2026, 14:20 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6h7w-fc84-x7p6)

## Sources

- [GitHub Advisory Database: GHSA-6h7w-fc84-x7p6](https://github.com/advisories/GHSA-6h7w-fc84-x7p6)
- [OSV: GHSA-6h7w-fc84-x7p6](https://osv.dev/vulnerability/GHSA-6h7w-fc84-x7p6)
- <https://github.com/http4s/http4s/security/advisories/GHSA-6h7w-fc84-x7p6>
- <https://nvd.nist.gov/vuln/detail/CVE-2021-32643>
- <https://github.com/http4s/http4s/commit/52e1890665410b4385e37b96bc49c5e3c708e4e9>
- <https://mvnrepository.com/artifact/org.http4s/http4s-core>

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-6h7w-fc84-x7p6>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-6h7w-fc84-x7p6/>. Everything for agents: <https://agentprime.io/llms.txt>.
