# CVE-2026-69201: Http4s: ResourceService and Webjar Service path escape via percent-encoded separators > Attackers can access classpath resources outside the configured base via percent-encoded separators in Http4s ResourceService and WebjarService. - **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 Sep 2026 - **Updated:** 15 Sep 2026 - **Also known as:** GHSA-crq5-92j2-j7wv ## What is CVE-2026-69201? CVE-2026-69201 is a medium-severity path traversal vulnerability in http4s, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, ResourceService and WebjarService decode each URL path segment but reject only segments exactly equal to an empty string, a dot, or two dots. A request containing percent-encoded slash or backslash separators can turn an accepted segment into a parent-directory traversal after decoding, allowing access to classpath or WebJar resources outside the configured base when a directory-backed classpath is served and the backend preserves the encoded separator. The patch rejects decoded segments containing slash or backslash in ResourceService and WebjarService, and applies the same guard to the non-exploitable FileService for consistency. This issue is fixed in versions 0.23.35 and 1.0.0-M47. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2026-69201? 10 open source packages ship an affected version, including org.http4s:http4s-server_2.13, org.http4s:http4s-server_2.12 and org.http4s:http4s-server_3. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.http4s:http4s-server_2.13` | Maven | All versions | 0.23.35 | | `org.http4s:http4s-server_2.13` | Maven | All versions | 0.23.35 | | `org.http4s:http4s-server_2.13` | Maven | From 1.0.0-M1 | 1.0.0-M47 | | `org.http4s:http4s-server_2.13` | Maven | From 1.0.0-M1 | 1.0.0-M47 | | `org.http4s:http4s-server_2.12` | Maven | All versions | 0.23.35 | | `org.http4s:http4s-server_2.12` | Maven | All versions | 0.23.35 | | `org.http4s:http4s-server_3` | Maven | All versions | 0.23.35 | | `org.http4s:http4s-server_3` | Maven | All versions | 0.23.35 | | `org.http4s:http4s-server_3` | Maven | From 1.0.0-M1 | 1.0.0-M47 | | `org.http4s:http4s-server_3` | Maven | From 1.0.0-M1 | 1.0.0-M47 | ## How do I fix CVE-2026-69201? Upgrade org.http4s:http4s-server_2.13 to a fixed version for your release line: 0.23.35 or 1.0.0-M47. ## Is CVE-2026-69201 being exploited? There is no known exploitation of CVE-2026-69201 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-69201 and fix it if it is affected. What it is: CVE-2026-69201 is a medium-severity path traversal vulnerability in http4s, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-69201 in the wild and no public exploit code. Affected packages and fixed versions: - org.http4s:http4s-server_2.13 (Maven): affected all versions; fixed in 0.23.35 - org.http4s:http4s-server_2.13 (Maven): affected all versions; fixed in 0.23.35 - org.http4s:http4s-server_2.13 (Maven): affected from 1.0.0-M1; fixed in 1.0.0-M47 - org.http4s:http4s-server_2.13 (Maven): affected from 1.0.0-M1; fixed in 1.0.0-M47 - org.http4s:http4s-server_2.12 (Maven): affected all versions; fixed in 0.23.35 - org.http4s:http4s-server_2.12 (Maven): affected all versions; fixed in 0.23.35 - org.http4s:http4s-server_3 (Maven): affected all versions; fixed in 0.23.35 - org.http4s:http4s-server_3 (Maven): affected all versions; fixed in 0.23.35 - org.http4s:http4s-server_3 (Maven): affected from 1.0.0-M1; fixed in 1.0.0-M47 - org.http4s:http4s-server_3 (Maven): affected from 1.0.0-M1; fixed in 1.0.0-M47 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-69201/ (Markdown: https://insights.sbomify.com/CVE-2026-69201/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-69201 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-69201 - OSV: https://osv.dev/vulnerability/CVE-2026-69201 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-69201/ Summaries are generated and may contain mistakes; the official description above is the record.