# CVE-2021-39185: Default CORS config allows any origin with credentials

> Default CORS configuration in Http4s allows origin reflection and null origin attacks, enabling cross-origin data access.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 1 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-52cf-226f-rhr6

## What is CVE-2021-39185?

CVE-2021-39185 is a critical vulnerability in http4s, published on 1 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-346 (Origin Validation Error)

## Which versions are affected by CVE-2021-39185?

22 open source packages ship an affected version, including org.http4s:http4s-server_2.12, org.http4s:http4s-server_2.10 and org.http4s:http4s-server_2.11. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.http4s:http4s-server_2.12` | Maven | All versions | 0.21.27 |
| `org.http4s:http4s-server_2.12` | Maven | All versions | 0.21.27 |
| `org.http4s:http4s-server_2.12` | Maven | From 0.22.0 | 0.22.3 |
| `org.http4s:http4s-server_2.12` | Maven | From 0.22.0 | 0.22.3 |
| `org.http4s:http4s-server_2.12` | Maven | From 0.23.0 | 0.23.2 |
| `org.http4s:http4s-server_2.12` | Maven | From 0.23.0 | 0.23.2 |
| `org.http4s:http4s-server_2.10` | Maven | All versions | None |
| `org.http4s:http4s-server_2.10` | Maven | All versions | None |
| `org.http4s:http4s-server_2.11` | Maven | All versions | None |
| `org.http4s:http4s-server_2.11` | Maven | All versions | None |
| `org.http4s:http4s-server_2.13` | Maven | All versions | 0.21.27 |
| `org.http4s:http4s-server_2.13` | Maven | All versions | 0.21.27 |
| `org.http4s:http4s-server_2.13` | Maven | From 0.22.0 | 0.22.3 |
| `org.http4s:http4s-server_2.13` | Maven | From 0.22.0 | 0.22.3 |
| `org.http4s:http4s-server_2.13` | Maven | From 0.23.0 | 0.23.2 |
| `org.http4s:http4s-server_2.13` | Maven | From 0.23.0 | 0.23.2 |
| `org.http4s:http4s-server_2.13.0-M5` | Maven | All versions | None |
| `org.http4s:http4s-server_2.13.0-M5` | Maven | All versions | None |
| `org.http4s:http4s-server_3` | Maven | From 0.22.0 | 0.22.3 |
| `org.http4s:http4s-server_3` | Maven | From 0.22.0 | 0.22.3 |
| `org.http4s:http4s-server_3` | Maven | From 0.23.0 | 0.23.2 |
| `org.http4s:http4s-server_3` | Maven | From 0.23.0 | 0.23.2 |

Products: Typelevel Http4s.

## How do I fix CVE-2021-39185?

Upgrade org.http4s:http4s-server_2.12 to a fixed version for your release line: 0.21.27, 0.22.3 or 0.23.2.

## Is CVE-2021-39185 being exploited?

There is no known exploitation of CVE-2021-39185 in the wild and no public exploit code.

## Other vulnerabilities in http4s

- [CVE-2021-41084](https://insights.sbomify.com/CVE-2021-41084/): Response Splitting from unsanitized headers in http4s (high 8.7)
- [CVE-2020-5280](https://insights.sbomify.com/CVE-2020-5280/): Local file inclusion vulnerability in http4s (high 7.6)
- [CVE-2023-22465](https://insights.sbomify.com/CVE-2023-22465/): Http4s has fatal error parsing User-Agent and Server headers (high 7.5)
- [CVE-2021-21294](https://insights.sbomify.com/CVE-2021-21294/): Unbounded connection acceptance in http4s-blaze-server (high 7.5)
- [CVE-2025-59822](https://insights.sbomify.com/CVE-2025-59822/): Http4s vulnerable to HTTP Request Smuggling due to improper handling of HTTP trailer section (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-39185 and fix it if it is affected.

What it is: CVE-2021-39185 is a critical vulnerability in http4s, published on 1 Sep 2021. 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-2021-39185 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.http4s:http4s-server_2.12 (Maven): affected all versions; fixed in 0.21.27
- org.http4s:http4s-server_2.12 (Maven): affected all versions; fixed in 0.21.27
- org.http4s:http4s-server_2.12 (Maven): affected from 0.22.0; fixed in 0.22.3
- org.http4s:http4s-server_2.12 (Maven): affected from 0.22.0; fixed in 0.22.3
- org.http4s:http4s-server_2.12 (Maven): affected from 0.23.0; fixed in 0.23.2
- org.http4s:http4s-server_2.12 (Maven): affected from 0.23.0; fixed in 0.23.2
- org.http4s:http4s-server_2.10 (Maven): affected all versions; no fix listed
- org.http4s:http4s-server_2.10 (Maven): affected all versions; no fix listed
- org.http4s:http4s-server_2.11 (Maven): affected all versions; no fix listed
- org.http4s:http4s-server_2.11 (Maven): affected all versions; no fix listed
- org.http4s:http4s-server_2.13 (Maven): affected all versions; fixed in 0.21.27
- org.http4s:http4s-server_2.13 (Maven): affected all versions; fixed in 0.21.27

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-2021-39185/ (Markdown: https://insights.sbomify.com/CVE-2021-39185/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-39185
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-39185
- OSV: https://osv.dev/vulnerability/CVE-2021-39185

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-39185/
Summaries are generated and may contain mistakes; the official description above is the record.
