Skip to content
Fencer Vulns
medium 4.3

CVE-2025-2786 json

Tempo-operator: serviceaccount token exposure leading to token and subject access reviews in openshift tempo operator

published 2025-04-02 19 mo ago modified 2026-09-08 2 mo ago also GHSA-28gr-56hr-prp6 , GO-2026-4996 , EUVD-2025-9524

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 31%
public exploits
0
none known

Summary

A flaw was found in Tempo Operator, where it creates a ServiceAccount, ClusterRole, and ClusterRoleBinding when a user deploys a TempoStack or TempoMonolithic instance. This flaw allows a user with full access to their namespace to extract the ServiceAccount token and use it to submit TokenReview and SubjectAccessReview requests, potentially revealing information about other users' permissions. While this does not allow privilege escalation or impersonation, it exposes information that could aid in gathering information for further attacks.

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-2786 updated cvss 4.3

tempo-operator: ServiceAccount Token Exposure Leading to Token and Subject Access Reviews in OpenShift Tempo Operator

  • 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.38% chance of exploitation in the next 30 days, higher than 31% 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.