CVE-2025-2786VulnerabilityPublished 4 Apr 2025Updated 25 Oct 2026

Red Hat Security Advisory: Red Hat OpenShift distributed tracing platform (Tempo) 3.5.1 release

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

CVE-2025-2842

Not known to be exploited.

Data as of 26 Oct 2026, 08:30 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Apr 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Red Hat Product Security Red Hat	Affected >=3.5.0 <=3.5.1 =0 Red Hat Red Hat OpenShift distributed tracing Red Hat OpenShift distributed tracing 3.5.2 amd64 registry.redhat.io/rhosdt/tempo-operator-bundle@sha256:295309554800a4a1d5d0646c8ec776e2f712cd13cebb085078df5ba85d604808_amd64 0 Red Hat OpenShift distributed tracing 3.5.3 Red Hat OpenShift distributed tracing 3.5	Fixed in–

AI-suggested

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.

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.

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.

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.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-405Asymmetric Resource Consumption (Amplification) (opens in a new tab)
Class weakness
The product does not properly control situations in which an adversary can cause the product to consume or produce excessive resources without requiring the adversary to invest equivalent work or otherwise prove authorization, i.e., the adversary's influence is "asymmetric."
Architecture and Design
An application must make resources available to a client commensurate with the client's access level.
Architecture and Design
An application must, at all times, keep track of allocated resources and meter their usage appropriately.
System Configuration
Consider disabling resource-intensive algorithms on the server side, such as Diffie-Hellman key exchange.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Aug 2026, 22:10 UTC

WeaknessesCWE-200, CWE-405

Technical details

References

Community reviews

Related threats