CVE-2026-107912
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.
Statement
The Red Hat Product Security team has assessed the severity of this vulnerability as Important, given that it allows for a complete bypass of authorization rules on management endpoints. Successful exploitation allows an attacker to access sensitive management data and perform unauthorized configuration changes. The vulnerability's root cause is an improper path concatenation mechanism when applying security policies to the management interface.
Mitigation
--- CME Mitigation Guidance (2026-11-06) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to ensure slash delimiter separation when joining the management root path with permission rules in quarkus-vertx-http to prevent authorization bypass on management endpoints: upgrade to the corresponding fixed Red Hat builds, which inserts a slash delimiter when concatenating the management root path with relative permission rules so policies bind to actual endpoints rather than malformed paths, closing direct HTTP requests to exposed management paths. Until patched, this is a concern on Quarkus applications exposing the management interface to local or private network callers across all platforms, so restrict network and local access to the Quarkus management interface to trusted administrators, preventing untrusted callers from reaching exposed endpoints. As a compensating measure, restrict network access to the port exposing the Quarkus management interface using host-based firewalls such as firewalld or nftables and record administrative actions executed through the management interface and forward logs to a SIEM to detect unauthorized configuration changes. These controls limit blast radius and contain exploitation, but they do not fix the underlying improper path concatenation defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-909 Default-Deny API Authorization Policy (high)
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.7 | N/A | 7.7 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
cve.org: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Application Data; Read Files or Directories
An attacker could read sensitive data, either by reading the data directly from a data store that is not restricted, or by accessing insufficiently-protected, privileged functionality to read the data.
Integrity
Technical Impact: Modify Application Data; Modify Files or Directories
An attacker could modify sensitive data, either by writing the data directly to a data store that is not restricted, or by accessing insufficiently-protected, privileged functionality to write the data.
Access Control
Technical Impact: Gain Privileges or Assume Identity; Bypass Protection Mechanism
An attacker could gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)
An attacker could gain unauthorized access to resources on the system and excessively consume those resources, leading to a denial of service.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
