CVE-2025-2842 Tempo-operator: tempo operator token exposition lead to read sensitive data
Attackers with specific namespace permissions can read service account tokens to access all cluster metrics when Jaeger UI monitoring is enabled.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-2842?
CVE-2025-2842 is a medium-severity vulnerability in Red Hat OpenShift distributed tracing 3, published on 2 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-200
Which versions are affected by CVE-2025-2842?
3 open source packages ship an affected version, including github.com/grafana/tempo-operator.
| Package | Affected | Fixed in |
|---|---|---|
github.com/grafana/tempo-operator Go | All versions | 0.16.0 |
github.com/grafana/tempo-operator Go | All versions | 0.16.0 |
github.com/grafana/tempo-operator Go | All versions | 0.16.0 |
How do I fix CVE-2025-2842?
Upgrade github.com/grafana/tempo-operator to 0.16.0 or later.
Is CVE-2025-2842 being exploited?
There is no known exploitation of CVE-2025-2842 in the wild and no public exploit code.
Sources
Also known as GHSA-5xf3-gmx4-529v, GO-2026-5161.