# CVE-2025-2786: Tempo-operator: serviceaccount token exposure leading to token and subject access reviews in openshift tempo operator > Attackers with namespace access can extract ServiceAccount tokens to reveal other users' permissions via TokenReview and SubjectAccessReview requests. - **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 2 Apr 2025 - **Updated:** 8 Sep 2026 - **Also known as:** GHSA-28gr-56hr-prp6, GO-2026-4996 ## What is CVE-2025-2786? CVE-2025-2786 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 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. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2025-2786? 3 open source packages ship an affected version, including github.com/grafana/tempo-operator. | Package | Ecosystem | 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-2786? Upgrade github.com/grafana/tempo-operator to 0.16.0 or later. ## Is CVE-2025-2786 being exploited? There is no known exploitation of CVE-2025-2786 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-2786 and fix it if it is affected. What it is: CVE-2025-2786 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. Exploitation: There is no known exploitation of CVE-2025-2786 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/grafana/tempo-operator (Go): affected all versions; fixed in 0.16.0 - github.com/grafana/tempo-operator (Go): affected all versions; fixed in 0.16.0 - github.com/grafana/tempo-operator (Go): affected all versions; fixed in 0.16.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-2786/ (Markdown: https://insights.sbomify.com/CVE-2025-2786/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2786 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2786 - OSV: https://osv.dev/vulnerability/CVE-2025-2786 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-2786/ Summaries are generated and may contain mistakes; the official description above is the record.