Exploit Intelligence: Missing Authorization
CVE-2026-107912 is a high-severity missing authorization vulnerability in Exploit Intelligence from Red Hat, with a CVSS 3.1 base score of 7.7 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.17% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Exploit Intelligence you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Red Hat | Exploit Intelligence | Not specified in the record | Not stated |
| Red Hat | OpenShift Serverless | Not specified in the record | Not stated |
| Red Hat | Red Hat build of Apache Camel 4 for Quarkus 3 | Not specified in the record | Not stated |
| Red Hat | Red Hat build of Apicurio Registry 3 | Not specified in the record | Not stated |
| Red Hat | Red Hat build of Debezium 3 | Not specified in the record | Not stated |
| Red Hat | Red Hat Build of Keycloak | Not specified in the record | Not stated |
| Red Hat | Red Hat build of Quarkus | Not specified in the record | Not stated |
| Red Hat | Red Hat Fuse 7 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift AI (RHOAI) | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Dev Spaces | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. Scored by CNA (redhat.com).
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authorization
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
How developers prevent this class of flaw
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
References
Other references
Other vulnerabilities in Exploit Intelligence
- 9.1 Critical severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 9.1 Critical severity
- 9.8 Critical severity
Recent Missing Authorization vulnerabilities
- 8.1 High severity
- 7.1 High severity
- 8.5 High severity
- 8.1 High severity
- 8.1 High severity
- 9.8 Critical severity
Spotted an error? Tell us.