Io.quarkus/quarkus-vertx-http: quarkus-vertx-http: authorization bypass in management interface via path concatenation flaw
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. A security policy is defined for a relative path on the management interface (for example, secret). The management root path is set to /q without a trailing slash, which is the default.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 29/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The Quarkus framework's quarkus-vertx-http component has an authorization bypass in its management interface. A local attacker who does not need to log in can reach sensitive management endpoints that should be protected.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
A flaw was found in the management interface of the Quarkus framework, specifically within the quarkus-vertx-http component. The issue occurs when the framework incorrectly combines the management root path with specific permission rules, leading to a situation where security policies are applied to the wrong internal paths. As a result, an attacker can bypass intended authorization checks and gain unauthorized access to sensitive management endpoints.
cve.now Index
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach10/20Shipped in major Linux distributions
- Severity8.7/10CVSS 7.7, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 79 if added to CISA KEV
- Would score about 74 if CISA's SSVC rates exploitation active
- Would score about 39 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
A security policy is defined for a relative path on the management interface (for example, secret). The management root path is set to /q without a trailing slash, which is the default.Workaround: The checked facts do not list a workaround. The flaw depends on a security policy on a relative management path and on the default /q management root, so those are the settings to review while waiting for a fix.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- exploit-intelligence/agent-client-rhel9
Version range not reported
- openshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9
Version range not reported
- openshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9
Version range not reported
- openshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9
Version range not reported
- openshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9
Version range not reported
- openshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9
Version range not reported
- openshift-serverless-1/kn-eventing-integrations-aws-sqs-source-rhel9
Version range not reported
- openshift-serverless-1/kn-eventing-integrations-log-sink-rhel9
Version range not reported
Show all 20 packagesShow fewer packages
- openshift-serverless-1/kn-eventing-integrations-timer-source-rhel9
Version range not reported
- openshift-serverless-1/logic-rhel9-operator
Version range not reported
- quarkus-vertx-http
Version range not reported
- quarkus-vertx-http
Version range not reported
- quarkus-vertx-http
Version range not reported
- quarkus-vertx-http
Version range not reported
- rhbk/keycloak-rhel9
Version range not reported
- rhbk/keycloak-rhel9-operator
Version range not reported
- quarkus-vertx-http
Version range not reported
- quarkus-vertx-http
Version range not reported
- rhoai/odh-trustyai-service-rhel9
Version range not reported
- devspaces/multicluster-redirector-rhel9
Version range not reported
Evidence 2
- Report
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-107912
Is CVE-2026-107912 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A security policy set on a relative path of the management interface, such as secret, can be bypassed because of a path concatenation flaw. A successful bypass gives access to protected management endpoints, which can expose sensitive internal information and allow management configuration to be changed.Source: bugzilla.redhat.com
Am I affected, and how do I check?
The flaw needs a security policy defined on a relative path of the management interface, with the management root at its default /q without a trailing slash. The checked facts do not list affected version ranges, so check your Quarkus or Red Hat product version against the vendor advisory and confirm the management root and policy settings in your configuration.Source: bugzilla.redhat.com
How do I fix CVE-2026-107912?
The checked facts do not name a fixed version, so no upgrade target can be given from them. Check the vendor advisory for the first release that includes the fix for your product.Source: bugzilla.redhat.com
What if there's no patch?
The checked facts do not list a workaround. The flaw depends on a security policy on a relative management path and on the default /q management root, so those are the settings to review while waiting for a fix.Source: bugzilla.redhat.com