How severe is GHSA-g56w-cwg4-hxx9?

GHSA-g56w-cwg4-hxx9 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-g56w-cwg4-hxx9?

GHSA-g56w-cwg4-hxx9 affects the following packages: io.quarkus:quarkus-vertx-http-deployment (Maven), io.quarkus:quarkus-vertx-http-deployment (Maven). Ecosystems affected: Maven.

How do I fix GHSA-g56w-cwg4-hxx9?

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

How do I detect GHSA-g56w-cwg4-hxx9 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-deployment, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-g56w-cwg4-hxx9 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 GHSA-g56w-cwg4-hxx9?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g56w-cwg4-hxx9 can be triaged on real exposure rather than presence alone.

Is GHSA-g56w-cwg4-hxx9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-g56w-cwg4-hxx9 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 is the EPSS score for GHSA-g56w-cwg4-hxx9?

GHSA-g56w-cwg4-hxx9 has an EPSS (Exploit Prediction Scoring System) score of 32.5%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

When was GHSA-g56w-cwg4-hxx9 published, and has it been updated?

GHSA-g56w-cwg4-hxx9 was published on November 22, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

GHSA-g56w-cwg4-hxx9 — quarkus-vertx-http-deploy…

CRITICAL

GHSA-g56w-cwg4-hxx9 is a critical-severity (CVSS 9.8) remote code execution vulnerability in io.quarkus:quarkus-vertx-http-deployment. EPSS puts its 30-day exploitation probability at 32.5% (98th percentile). A fix is available for io.quarkus:quarkus-vertx-http-deployment — see the affected versions and patch details below.

Code injection in quarkus dev ui config editor

Also known asCVE-2022-4116

Published

Nov 22, 2022

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-g56w-cwg4-hxx9.

EPSS Exploitation Probability

via FIRST.org ↗

32.5%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-g56w-cwg4-hxx9 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 376,715 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

2 pkgs affected

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

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

A vulnerability was found in quarkus. This security flaw happens in Dev UI Config Editor which is vulnerable to drive-by localhost attacks leading to remote code execution.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.quarkus:quarkus-vertx-http-deployment`	≥ 2.14.0&&< 2.14.2.Final	2.14.2.Final`io.quarkus:quarkus-vertx-http-deployment:2.14.2.Final`
☕Maven	`io.quarkus:quarkus-vertx-http-deployment`	all versions	2.13.5.Final`io.quarkus:quarkus-vertx-http-deployment: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-deployment, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.quarkus:quarkus-vertx-http-deployment to 2.14.2.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g56w-cwg4-hxx9 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g56w-cwg4-hxx9 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-g56w-cwg4-hxx9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat build of Quarkus 2.13.5	see advisory	RHSA-2022:9023
Red Hat build of Quarkus Platform 2.7.6.SP3	`quarkus_dev_ui`	RHSA-2022:8957

Frequently Asked Questions

A vulnerability was found in quarkus. This security flaw happens in Dev UI Config Editor which is vulnerable to drive-by localhost attacks leading to remote code execution.

O3 Security · Impact-Aware SCA

Is GHSA-g56w-cwg4-hxx9 in your dependencies?

O3 Security finds GHSA-g56w-cwg4-hxx9 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works