Skip to content
Fencer Vulns
medium 4.3

CVE-2025-2842 json

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

published 2025-04-02 19 mo ago modified 2026-09-08 2 mo ago also GHSA-5xf3-gmx4-529v , GO-2026-5161 , EUVD-2025-9549

cvss
4.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 34%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/grafana/tempo-operator 0.16.0
  • Red Hat Red Hat OpenShift distributed tracing 3.5.3 rhosdt-3.5-1743162265, rhosdt-3.5-1744028971
  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-2842 updated cvss 4.3

tempo-operator: Tempo Operator Token Exposition lead to read sensitive data

  • Red Hat OpenShift distributed tracing 3 rhosdt/tempo-rhel8, rhosdt/tempo-query-rhel8, rhosdt/tempo-gateway-rhel8, rhosdt/tempo-gateway-opa-rhel8, rhosdt/tempo-jaeger-query-rhel8
    affected: workaround, no fix available “Currently, no mitigation is available for this vulnerability.”
  • Red Hat OpenShift distributed tracing 3.5.3 rhosdt rhosdt-3.5-1743162265, rhosdt rhosdt-3.5-1744028971
    fixed: vendor fix “Currently, no mitigation is available for this vulnerability.” RHSA-2025:3607
  • Red Hat OpenShift distributed tracing 3.5.3 rhosdt rhosdt-3.5-1743162273, rhosdt rhosdt-3.5-1743162275, rhosdt rhosdt-3.5-1743162349, rhosdt rhosdt-3.5-1743162375, rhosdt rhosdt-3.5-1743172309, rhosdt rhosdt-3.5-1744029015, +5 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
19 mo ago

Exploit prediction

0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/grafana/tempo-operator
<0.16.0
0.16.0

Affected products

  • Red Hat Red Hat OpenShift distributed tracing 3.5.3
  • Red Hat Red Hat OpenShift distributed tracing 3

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.