Approved changes feed: RSS · Atom

cpe:2.3:a:typelevel:http4s:1.0.0:milestone1:*:*:*:*:*:*

part: a version: 1.0.0 update: milestone1

VendorTypelevel (ae0d1341-5b6f-53da-b68c-914a850a6910)
ProductHttp4S (a2122f7e-d89a-58a8-8588-8921f089cb5b)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:github/http4s/http4s purl2cpe 2026-06-01 10:11:18.456160

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2025-59822 vulnerable 2026-06-08 07:35:23.223900 Http4s vulnerable to HTTP Request Smuggling due to improper handling of HTTP trailer section
Http4s is a Scala interface for HTTP services. In versions from 1.0.0-M1 to before 1.0.0-M45 and before 0.23.31, http4s is vulnerable to HTTP Request Smuggling due to improper handling of HTTP trailer section. This vulnerability could enable attackers to bypass front-end servers security controls, launch targeted attacks against active users, and poison web caches. A pre-requisite for exploitation involves the web application being deployed behind a reverse-proxy that forwards trailer headers. This issue has been patched in versions 1.0.0-M45 and 0.23.31.
Published: 2025-09-23T18:54:42.867Z
Updated: 2025-09-23T19:17:26.320Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-22465 vulnerable 2026-06-08 05:54:26.358274 Http4s has fatal error parsing User-Agent and Server headers
HIGH (7.5)
Http4s is a Scala interface for HTTP services. Starting with version 0.1.0 and prior to versions 0.21.34, 0.22.15, 0.23.17, and 1.0.0-M38, the `User-Agent` and `Server` header parsers are susceptible to a fatal error on certain inputs. In http4s, modeled headers are lazily parsed, so this only applies to services that explicitly request these typed headers. Fixes are released in 0.21.34, 0.22.15, 0.23.17, and 1.0.0-M38. As a workaround, use the weakly typed header interface.
Published: 2023-01-04T15:30:04.129Z
Updated: 2025-03-10T21:32:44.734Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-41084 vulnerable 2026-06-08 05:35:19.687720 Response Splitting from unsanitized headers in http4s
HIGH (8.7)
http4s is an open source scala interface for HTTP. In affected versions http4s is vulnerable to response-splitting or request-splitting attacks when untrusted user input is used to create any of the following fields: Header names (`Header.name`å), Header values (`Header.value`), Status reason phrases (`Status.reason`), URI paths (`Uri.Path`), URI authority registered names (`URI.RegName`) (through 0.21). This issue has been resolved in versions 0.21.30, 0.22.5, 0.23.4, and 1.0.0-M27 perform the following. As a matter of practice http4s services and client applications should sanitize any user input in the aforementioned fields before returning a request or response to the backend. The carriage return, newline, and null characters are the most threatening.
Published: 2021-09-21T17:20:14.000Z
Updated: 2024-08-04T02:59:31.504Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-39185 vulnerable 2026-06-08 05:33:49.141122 Default CORS config allows any origin with credentials
CRITICAL (9.1)
Http4s is a minimal, idiomatic Scala interface for HTTP services. In http4s versions 0.21.26 and prior, 0.22.0 through 0.22.2, 0.23.0, 0.23.1, and 1.0.0-M1 through 1.0.0-M24, the default CORS configuration is vulnerable to an origin reflection attack. The middleware is also susceptible to a Null Origin Attack. The problem is fixed in 0.21.27, 0.22.3, 0.23.2, and 1.0.0-M25. The original `CORS` implementation and `CORSConfig` are deprecated. See the GitHub GHSA for more information, including code examples and workarounds.
Published: 2021-09-01T19:25:09.000Z
Updated: 2024-08-04T01:58:18.235Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2021-32643 vulnerable 2026-06-08 05:32:07.749317 StaticFile.fromUrl can leak presence of a directory
MEDIUM (5.8)
Http4s is a Scala interface for HTTP services. `StaticFile.fromUrl` can leak the presence of a directory on a server when the `URL` scheme is not `file://`, and the URL points to a fetchable resource under its scheme and authority. The function returns `F[None]`, indicating no resource, if `url.getFile` is a directory, without first checking the scheme or authority of the URL. If a URL connection to the scheme and URL would return a stream, and the path in the URL exists as a directory on the server, the presence of the directory on the server could be inferred from the 404 response. The contents and other metadata about the directory are not exposed. This affects http4s versions: 0.21.7 through 0.21.23, 0.22.0-M1 through 0.22.0-M8, 0.23.0-M1, and 1.0.0-M1 through 1.0.0-M22. The [patch](https://github.com/http4s/http4s/commit/52e1890665410b4385e37b96bc49c5e3c708e4e9) is available in the following versions: v0.21.24, v0.22.0-M9, v0.23.0-M2, v1.0.0-M23. As a workaround users can avoid calling `StaticFile.fromUrl` with non-file URLs.
Published: 2021-05-27T17:15:11.000Z
Updated: 2024-08-03T23:25:30.936Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.