Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Workaround
There is no mitigation or workaround other than upgrading to tempo-operator.v0.21.0-2 (or later); until upgraded, administrators requiring strict namespace isolation of trace data should not rely on query RBAC alone and should consider restricting access to the Tempo query API at the network/route level as a temporary compensating control.
Tracking
Sign in to view the affected projects.
No advisories yet.
Mon, 13 Jul 2026 12:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The Tempo Operator's gateway component failed to consistently apply namespace-scoped redaction on some query API response paths when query RBAC was enabled, allowing an authenticated user to read span attributes belonging to other tenants' namespaces. | |
| Title | Tempo-operator: tempo operator: query rbac bypass | |
| First Time appeared |
Redhat
Redhat openshift Distributed Tracing |
|
| Weaknesses | CWE-863 | |
| CPEs | cpe:/a:redhat:openshift_distributed_tracing:3 | |
| Vendors & Products |
Redhat
Redhat openshift Distributed Tracing |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-07-13T11:43:59.024Z
Reserved: 2026-07-13T11:29:50.979Z
Link: CVE-2026-62147
No data.
No data.
No data.
OpenCVE Enrichment
No data.