No advisories yet.
Solution
No solution given by the vendor.
Workaround
Do not set spec.routeHostName to values outside the operator's own namespace service names. Restrict which users can create or modify Hawtio custom resources via RBAC. Audit existing Hawtio CR instances for unexpected routeHostName values and rotate any TLS certificates that may have been issued with incorrect Common Names.
Tue, 08 Sep 2026 11:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in hawtio-operator. The operator reads the OpenShift Service CA private signing key from the openshift-service-ca namespace and uses it to mint client certificates with a Subject Common Name (CN) supplied by the author of a namespaced Hawtio custom resource. Because the operator ships a ClusterRole that aggregates Hawtio CR permissions into the edit and admin roles, any user with edit access in any namespace can obtain a Service-CA-signed certificate with an arbitrary subject. This certificate can be used to impersonate any in-cluster service identity to peers that trust the Service CA for client authentication, including Jolokia agents and other Service-CA-trusting components. | |
| Title | Hawtio-operator: hawtio-operator: service-ca signing oracle allows arbitrary-cn certificate issuance to namespace edit users | |
| First Time appeared |
Redhat
Redhat apache Camel Hawtio |
|
| Weaknesses | CWE-295 | |
| CPEs | cpe:/a:redhat:apache_camel_hawtio:4 | |
| Vendors & Products |
Redhat
Redhat apache Camel Hawtio |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-09-08T11:27:52.787Z
Reserved: 2026-08-27T10:25:52.070Z
Link: CVE-2026-78234
No data.
No data.
No data.
OpenCVE Enrichment
No data.