Red Hat Security Advisory: Red Hat OpenShift distributed tracing platform (Tempo) 3.5.1 release
Release of Red Hat OpenShift distributed tracing provides following security improvements, bug fixes, and new features. The Red Hat OpenShift distributed tracing (Tempo) 3.5.1 is based on the open source link:https://grafana.com/oss/tempo/[Grafana Tempo] release 2.7.1. Breaking changes: * With this update, for a user to create or modify a TempoStack or TempoMonolithic CR with enabled multi-tenancy, the user must have permissions to create a TokenReview and SubjectAccessReview. Deprecations: * Nothing Technology Preview features: * Nothing Enhancements: * Nothing Bug fixes: * https://access.redhat.com/security/cve/CVE-2025-2786 * https://access.redhat.com/security/cve/CVE-2025-2842 Known issues: * Currently, when the OpenShift tenancy mode is enabled, the ServiceAccount of the gateway component of a TempoStack or TempoMonolithic instance requires the TokenReview and SubjectAccessReview permissions for authorization. Workaround: deploy the instance in a dedicated namespace, and carefully audit which users have permission to read the Secrets in this namespace.
AI Analysis
Technical Summary
The vulnerability CVE-2025-2786 in Red Hat OpenShift distributed tracing platform (Tempo) 3.5.1 arises from the Tempo Operator creating a ServiceAccount, ClusterRole, and ClusterRoleBinding when deploying TempoStack or TempoMonolithic instances. Users with full access to their namespace can extract the ServiceAccount token and use it to submit TokenReview and SubjectAccessReview requests. This behavior exposes information about other users' permissions within the cluster. Although this does not enable privilege escalation or impersonation, it leaks sensitive information that could facilitate further attacks. Red Hat has assigned a moderate impact rating and a CVSS v3.1 score of 4.3 (Low confidentiality impact, no integrity or availability impact). Currently, there is no available mitigation or patch for this issue. The advisory recommends careful auditing of permissions and namespace deployments as a workaround.
Potential Impact
The vulnerability allows users with full access to their namespace to extract a ServiceAccount token and perform TokenReview and SubjectAccessReview requests, potentially disclosing information about other users' permissions in the cluster. This information exposure does not permit privilege escalation or impersonation but may assist attackers in reconnaissance for further attacks. The confidentiality impact is low, and there is no impact on integrity or availability. Red Hat rates the impact as moderate with a CVSS base score of 4.3.
Mitigation Recommendations
Currently, no official mitigation or patch is available for this vulnerability. As a workaround, it is recommended to deploy TempoStack or TempoMonolithic instances in dedicated namespaces and carefully audit which users have permission to read Secrets in these namespaces. Monitor Red Hat advisories for updates or patches addressing this issue.
Red Hat Security Advisory: Red Hat OpenShift distributed tracing platform (Tempo) 3.5.1 release
Description
Release of Red Hat OpenShift distributed tracing provides following security improvements, bug fixes, and new features. The Red Hat OpenShift distributed tracing (Tempo) 3.5.1 is based on the open source link:https://grafana.com/oss/tempo/[Grafana Tempo] release 2.7.1. Breaking changes: * With this update, for a user to create or modify a TempoStack or TempoMonolithic CR with enabled multi-tenancy, the user must have permissions to create a TokenReview and SubjectAccessReview. Deprecations: * Nothing Technology Preview features: * Nothing Enhancements: * Nothing Bug fixes: * https://access.redhat.com/security/cve/CVE-2025-2786 * https://access.redhat.com/security/cve/CVE-2025-2842 Known issues: * Currently, when the OpenShift tenancy mode is enabled, the ServiceAccount of the gateway component of a TempoStack or TempoMonolithic instance requires the TokenReview and SubjectAccessReview permissions for authorization. Workaround: deploy the instance in a dedicated namespace, and carefully audit which users have permission to read the Secrets in this namespace.
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability CVE-2025-2786 in Red Hat OpenShift distributed tracing platform (Tempo) 3.5.1 arises from the Tempo Operator creating a ServiceAccount, ClusterRole, and ClusterRoleBinding when deploying TempoStack or TempoMonolithic instances. Users with full access to their namespace can extract the ServiceAccount token and use it to submit TokenReview and SubjectAccessReview requests. This behavior exposes information about other users' permissions within the cluster. Although this does not enable privilege escalation or impersonation, it leaks sensitive information that could facilitate further attacks. Red Hat has assigned a moderate impact rating and a CVSS v3.1 score of 4.3 (Low confidentiality impact, no integrity or availability impact). Currently, there is no available mitigation or patch for this issue. The advisory recommends careful auditing of permissions and namespace deployments as a workaround.
Potential Impact
The vulnerability allows users with full access to their namespace to extract a ServiceAccount token and perform TokenReview and SubjectAccessReview requests, potentially disclosing information about other users' permissions in the cluster. This information exposure does not permit privilege escalation or impersonation but may assist attackers in reconnaissance for further attacks. The confidentiality impact is low, and there is no impact on integrity or availability. Red Hat rates the impact as moderate with a CVSS base score of 4.3.
Mitigation Recommendations
Currently, no official mitigation or patch is available for this vulnerability. As a workaround, it is recommended to deploy TempoStack or TempoMonolithic instances in dedicated namespaces and carefully audit which users have permission to read Secrets in these namespaces. Monitor Red Hat advisories for updates or patches addressing this issue.
Technical Details
- Gcve Source
- db.gcve.eu
- Csaf Category
- csaf_security_advisory
- Csaf Version
- 2.0
- Publisher
- Red Hat Product Security
- Advisory Id
- RHSA-2025:3607
- Cve Count
- 3
- Additional Cves
- ["CVE-2025-2842","CVE-2025-30204"]
Threat ID: 6a160973e29bf47b5063c532
Added to database: 05/26/2026, 20:58:27 UTC
Last enriched: 08/14/2026, 22:10:22 UTC
Last updated: 09/10/2026, 19:24:56 UTC
Views: 52
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.