CVE-2025-2786: Tempo-operator: serviceaccount token exposure leading to token and subject access reviews in openshift tempo operator
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.
Security readout for executives and security teams
Plain-English summary
Tempo Operator can expose an operator-created service account token to users who already control the associated namespace. That token may reveal information about other users’ permissions through Kubernetes review APIs. The flaw does not provide privilege escalation or impersonation, but the intelligence gathered could support later attacks.
Executive priority
Schedule remediation through the normal vulnerability-management cycle, prioritizing shared or less-trusted clusters. Escalate if broad namespace administration is delegated, credentials may have leaked, or audit logs show unexpected review requests. This is an information-exposure issue, not a demonstrated cluster takeover path.
Technical view
Deploying TempoStack or TempoMonolithic causes the operator to create a ServiceAccount, ClusterRole, and ClusterRoleBinding. A user with full namespace access can obtain the service account token and submit TokenReview or SubjectAccessReview requests. The reported impact is limited to confidentiality; CVSS 3.1 is 4.3 with no integrity or availability impact.
Likely exposure
Exposure is most likely in OpenShift clusters running the listed Red Hat OpenShift distributed tracing 3 or 3.5 Tempo components where untrusted or compromised users have full access to a namespace containing TempoStack or TempoMonolithic. The supplied data does not establish exposure for other Tempo Operator versions.
Exploitation context
The attacker must already have full access to the affected namespace. No user interaction is required, but the reported outcome is permission discovery rather than privilege escalation or impersonation. The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation.
Researcher notes
The vulnerability is categorized as CWE-200 and scored CVSS 3.1 4.3. Its security value lies in permission enumeration that could improve subsequent targeting. The supplied affected-product list mixes specific 3.5.2 builds with broader version 3 components, so validate exact package applicability through Red Hat’s advisories rather than extrapolating.
Mitigation direction
Apply the applicable Red Hat security errata after confirming affected component and build coverage.
Review Grafana Tempo Operator pull request 1145 and vendor guidance for the intended correction.
Restrict full namespace access to trusted administrators and necessary automation identities.
Rotate exposed service account credentials if investigation indicates unauthorized access.
Validation and detection
Inventory OpenShift distributed tracing and Tempo Operator versions against the vendor advisories.
Identify namespaces containing TempoStack or TempoMonolithic instances.
Inspect operator-created ServiceAccounts, ClusterRoles, and ClusterRoleBindings for the vulnerable permission design.
Review audit logs for unexpected TokenReview or SubjectAccessReview requests from Tempo service accounts.
Confirm vendor remediation is installed and affected credentials have been rotated where necessary.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-200 · source CWE mapping
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.