# CVE-2022-4147: Quarkus CORS filter allows simple GET and POST requests with an invalid Origin to proceed

> The Quarkus CORS filter incorrectly allows simple GET and POST requests with invalid Origin headers, bypassing cross-origin restrictions.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Dec 2022
- **Updated:** 14 Apr 2025
- **Also known as:** GHSA-9895-g6x5-xwcp

## What is CVE-2022-4147?

CVE-2022-4147 is a high-severity vulnerability in quarkus-2, published on 6 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Quarkus CORS filter allows simple GET and POST requests with invalid Origin to proceed. Simple GET or POST requests made with XMLHttpRequest are the ones which have no event listeners registered on the object returned by the XMLHttpRequest upload property and have no ReadableStream object used in the request.

Weakness: CWE-1026

## Which versions are affected by CVE-2022-4147?

4 open source packages ship an affected version, including io.quarkus:quarkus-vertx-http. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.quarkus:quarkus-vertx-http` | Maven | All versions | 2.13.5.Final |
| `io.quarkus:quarkus-vertx-http` | Maven | All versions | 2.13.5.Final |
| `io.quarkus:quarkus-vertx-http` | Maven | From 2.14.0.CR1 | 2.14.2.Final |
| `io.quarkus:quarkus-vertx-http` | Maven | From 2.14.0.CR1 | 2.14.2.Final |

Products: Quarkus Quarkus.

## How do I fix CVE-2022-4147?

Upgrade io.quarkus:quarkus-vertx-http to a fixed version for your release line: 2.13.5.Final or 2.14.2.Final.

## Is CVE-2022-4147 being exploited?

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

## Other vulnerabilities in quarkus-2

- [CVE-2022-4116](https://insights.sbomify.com/CVE-2022-4116/): Code injection in quarkus dev ui config editor (critical 9.8)
- [CVE-2022-2466](https://insights.sbomify.com/CVE-2022-2466/): Quarkus does not terminate HTTP requests header context (critical 9.8)
- [CVE-2024-12225](https://insights.sbomify.com/CVE-2024-12225/): Io.quarkus:quarkus-security-webauthn: quarkus webauthn unexpected authentication bypass (critical 9.1)
- [CVE-2026-39852](https://insights.sbomify.com/CVE-2026-39852/): Quarkus authorization bypass via semicolon path normalization inconsistency (high 8.8)
- [CVE-2022-0981](https://insights.sbomify.com/CVE-2022-0981/): Privilege escalation in quarkus (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4147 and fix it if it is affected.

What it is: CVE-2022-4147 is a high-severity vulnerability in quarkus-2, published on 6 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-4147 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.quarkus:quarkus-vertx-http (Maven): affected all versions; fixed in 2.13.5.Final
- io.quarkus:quarkus-vertx-http (Maven): affected all versions; fixed in 2.13.5.Final
- io.quarkus:quarkus-vertx-http (Maven): affected from 2.14.0.CR1; fixed in 2.14.2.Final
- io.quarkus:quarkus-vertx-http (Maven): affected from 2.14.0.CR1; fixed in 2.14.2.Final

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

## Sources

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

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