GHSA-4f4r-wgv2-jjvg — quarkus-vertx-http
HIGHGHSA-4f4r-wgv2-jjvg is a high-severity (CVSS 8.1) CWE-148 vulnerability in io.quarkus:quarkus-vertx-http. 1 public exploit reference exists, so weaponization risk is real. A fix is available for io.quarkus:quarkus-vertx-http — see the affected versions and patch details below.
Quarkus HTTP vulnerable to incorrect evaluation of permissions
EPSS Exploitation Probability
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-4f4r-wgv2-jjvg 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 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
io.quarkus:quarkus-vertx-http☕io.quarkus:quarkus-vertx-http☕io.quarkus:quarkus-vertx-http☕io.quarkus:quarkus-undertow☕io.quarkus:quarkus-undertow☕io.quarkus:quarkus-undertow☕io.quarkus:quarkus-csrf-reactive☕io.quarkus:quarkus-csrf-reactive+4 moreReal-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 flaw was found in Quarkus where HTTP security policies are not sanitizing certain character permutations correctly when accepting requests, resulting in incorrect evaluation of permissions. This issue could allow an attacker to bypass the security policy altogether, resulting in unauthorized endpoint access and possibly a denial of service.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.quarkus:quarkus-vertx-http | all versions | 2.16.11.Finalio.quarkus:quarkus-vertx-http:2.16.11.Final |
| ☕Maven | io.quarkus:quarkus-vertx-http | ≥ 3.0.0&&< 3.2.6.Final | 3.2.6.Finalio.quarkus:quarkus-vertx-http:3.2.6.Final |
| ☕Maven | io.quarkus:quarkus-vertx-http | ≥ 3.3.0&&< 3.3.3 | 3.3.3io.quarkus:quarkus-vertx-http:3.3.3 |
| ☕Maven | io.quarkus:quarkus-undertow | all versions | 2.16.11.Finalio.quarkus:quarkus-undertow:2.16.11.Final |
| ☕Maven | io.quarkus:quarkus-undertow | ≥ 3.0.0&&< 3.2.6.Final | 3.2.6.Finalio.quarkus:quarkus-undertow:3.2.6.Final |
| ☕Maven | io.quarkus:quarkus-undertow | ≥ 3.3.0&&< 3.3.3 | 3.3.3io.quarkus:quarkus-undertow:3.3.3 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkus:quarkus-vertx-http, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.quarkus:quarkus-vertx-http to 2.16.11.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4f4r-wgv2-jjvg 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-4f4r-wgv2-jjvg can be triaged on real exposure rather than presence alone.
Tailored to GHSA-4f4r-wgv2-jjvg. 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.
| Product | Fixed in | Advisory |
|---|---|---|
| Openshift Serverless 1 on RHEL 8 | openshift-serverless-clients-0:1.9.2-3.el8 | RHSA-2023:5479 |
| Red Hat build of OptaPlanner 8 | quarkus-vertx-http | RHSA-2023:5446 |
| Red Hat build of Quarkus 2.13.8.SP2 | io.quarkus/quarkus-keycloak-authorization:2.13.8.Final-redhat-00005 | RHSA-2023:5170 |
| Red Hat Camel Extensions for Quarkus 2.13.3-1 | quarkus-vertx-http | RHSA-2023:5310 |
| Red Hat OpenShift Serverless 1.30 | openshift-serverless-1/client-kn-rhel8:1.9.2-3 | RHSA-2023:5480 |
| RHEL-8 based Middleware Containers | rhpam-7/rhpam-kogito-builder-rhel8:7.13.4-3 | RHSA-2023:6107 |
| RHINT Camel-K-1.10.2 | quarkus-vertx-http | RHSA-2023:5337 |
| RHINT Service Registry 2.5.4 GA | quarkus-vertx-http | RHSA-2023:7653 |
Frequently Asked Questions
Is GHSA-4f4r-wgv2-jjvg in your dependencies?
O3 Security finds GHSA-4f4r-wgv2-jjvg across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.