Skip to content
OpenAdvisories
Medium · 4.3 CVE-2025-2842 EUVD-2025-9549GHSA-5xf3-gmx4-529vGO-2026-5161

Tempo-operator: tempo operator token exposition lead to read sensitive data

Published Apr 2, 2025 · Updated Sep 8, 2026 · Assigned by redhat

Description

A flaw was found in the Tempo Operator. When the Jaeger UI Monitor Tab functionality is enabled in a Tempo instance managed by the Tempo Operator, the Operator creates a ClusterRoleBinding for the Service Account of the Tempo instance to grant the cluster-monitoring-view ClusterRole.
This can be exploited if a user has 'create' permissions on TempoStack and 'get' permissions on Secret in a namespace (for example, a user has ClusterAdmin permissions for a specific namespace), as the user can read the token of the Tempo service account and therefore has access to see all cluster metrics.

Affected products

VendorProductAffectedFixed
— tempo-operator < 0.15.3 0.15.3
Red Hat Red Hat OpenShift distributed tracing 3.5.3 — —
Red Hat Red Hat OpenShift distributed tracing 3 — —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
openSUSE Leap 16.0 govulncheck-vulndb 0.0.20260723T184607-160000.1.1 openSUSE-SU-2026:21483-1

Affected packages

EcosystemPackageAffectedFixedRecord
Go github.com/grafana/tempo-operator < 0.16.0 0.16.0 GHSA-5xf3-gmx4-529v

Advisories 2

References