CVE-2025-2786 is a medium-severity (CVSS 4.3) Information Exposure vulnerability in github.com/grafana/tempo-operator. A fix is available for github.com/grafana/tempo-operator — see the affected versions and patch details below.
Tempo-operator: serviceaccount token exposure leading to token and subject access reviews in openshift tempo operator
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-2786.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/grafana/tempo-operatorReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/grafana/tempo-operator | all versions | 0.16.0go get github.com/grafana/tempo-operator@v0.16.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grafana/tempo-operator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/grafana/tempo-operator to 0.16.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-2786 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat has evaluated this vulnerability and rated with a Moderate impact as the attacker is limited to read access and requires previous permissions to read the token and get access to the cluster metrics.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift distributed tracing 3.5.3 | rhosdt/tempo-rhel8-operator:rhosdt-3.5-1743162265 | RHSA-2025:3607 |
| Red Hat OpenShift distributed tracing 3.5.3 | rhosdt/tempo-rhel8-operator:rhosdt-3.5-1744028971 | RHSA-2025:3740 |
Frequently Asked Questions
Is CVE-2025-2786 in your dependencies?
Find it across Go, including transitive dependencies.