How severe is CVE-2022-4147?

CVE-2022-4147 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-4147?

CVE-2022-4147 affects the following packages: io.quarkus:quarkus-vertx-http (Maven), io.quarkus:quarkus-vertx-http (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-4147?

Update io.quarkus:quarkus-vertx-http to 2.14.2.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-4147 is resolved across your whole dependency graph.

How do I detect CVE-2022-4147 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkus:quarkus-vertx-http. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2022-4147 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2022-4147?

O3 pinpoints whether CVE-2022-4147 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2022-4147 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-4147 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is CVE-2022-4147?

CVE-2022-4147 is classified as CWE-1026 (CWE-1026). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-4147 published, and has it been updated?

CVE-2022-4147 was published on December 6, 2022 and was last updated on July 15, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

CVE-2022-4147

HIGH

CVE-2022-4147 is a high-severity (CVSS 7.5) CWE-1026 vulnerability in io.quarkus:quarkus-vertx-http. O3 Security confirms whether CVE-2022-4147 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Quarkus CORS filter allows simple GET and POST requests with an invalid Origin to proceed

Also known asGHSA-9895-g6x5-xwcp

Published

Dec 6, 2022

Updated

Jul 15, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

☕io.quarkus:quarkus-vertx-http☕io.quarkus:quarkus-vertx-http

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.quarkus:quarkus-vertx-http`	≥ 2.14.0.CR1&&< 2.14.2.Final	2.14.2.Final
☕Maven	`io.quarkus:quarkus-vertx-http`	all versions	2.13.5.Final

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkus:quarkus-vertx-http. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update io.quarkus:quarkus-vertx-http to 2.14.2.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-4147 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2022-4147 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2022-4147. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-4147 in your dependencies?

O3 detects CVE-2022-4147 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works