CVE-2026-107912

Io.quarkus/quarkus-vertx-http: quarkus-vertx-http: authorization bypass in management interface via path concatenation flaw

  • High 7.7

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.

Key facts

Published
5 Nov 2026
Last changed
6 Nov 2026
Assigned by
redhat
EPSS
0.165% likely to be exploited in the next 30 days, higher than 5.786% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.7CVSS 3.1, Highfrom the CNA (redhat)CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

What to do

  • --- 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 CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

CNA context is abbreviated; consult the original record for the complete statements.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatExploit Intelligence
  • Default status: affected
Red HatOpenShift Serverless
  • Default status: affected
Red HatOpenShift Serverless
  • Default status: affected
Red HatOpenShift Serverless
  • Default status: affected
Red HatOpenShift Serverless
  • Default status: affected
Red HatOpenShift Serverless
  • Default status: affected
Red HatOpenShift Serverless
  • Default status: affected
Red HatOpenShift Serverless
  • Default status: affected
Red HatOpenShift Serverless
  • Default status: affected
Red HatOpenShift Serverless
  • Default status: affected
Red HatRed Hat build of Apache Camel 4 for Quarkus 3
  • Default status: affected
Red HatRed Hat build of Apicurio Registry 3
  • Default status: affected
Red HatRed Hat build of Debezium 3
  • Default status: affected
Red HatRed Hat Build of Keycloak
  • Default status: affected
Red HatRed Hat Build of Keycloak
  • Default status: affected
Red HatRed Hat Build of Keycloak
  • Default status: affected
Red HatRed Hat build of Quarkus
  • Default status: affected
Red HatRed Hat Fuse 7
  • Default status: unknown
Red HatRed Hat OpenShift AI (RHOAI)
  • Default status: affected
Red HatRed Hat OpenShift Dev Spaces
  • Default status: affected

Timeline

  1. 9 Oct 2026 Reported to Red Hat.
  2. 5 Nov 2026 Made public.
  3. 5 Nov 2026 Published

Weakness

References