CVE-2024-8260VulnerabilityPublished 11 Dec 2024Updated 7 Sep 2026

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

Affects Red HatSource GCVE Database

Not known to be exploited.

Data as of 26 Oct 2026, 06:26 UTC

Severity

Medium

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

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

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Dec 2024
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 2026-10-26.

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.4.0 <=3.4 Red Hat Red Hat OpenShift distributed tracing Red Hat OpenShift distributed tracing 3.4 amd64 registry.redhat.io/rhosdt/tempo-operator-bundle@sha256:a980e21c5cf96387bee07f2f271e73060bb5032ac969d678dc1f718841531ecb_amd64	Fixed in–

AI-suggested

Users should monitor Red Hat advisories for updates. Due to the limited attack vector, restricting local access to OPA CLI and careful control of input arguments can reduce risk. For detailed upgrade and operator management instructions, refer to Red Hat OpenShift documentation.

Description

Red Hat OpenShift distributed tracing platform based on Tempo. Tempo is an open-source, easy-to-use, and highly scalable distributed tracing backend. It provides observability for microservices architectures by allowing developers to track requests as they flow through distributed systems. Tempo is optimized to handle large volumes of trace data and is designed to be highly performant even under heavy loads. - https://docs.redhat.com/en/documentation/openshift_container_platform/4.17 /html/distributed_tracing/distributed-tracing-platform-tempo

Impact

If exploited, this vulnerability could allow an attacker with local access and control over OPA CLI arguments to force SMB authentication, potentially leading to unauthorized access or data manipulation. However, exploitation requires specific conditions, including direct access to the OPA CLI or Go library functions and the ability to influence input arguments, limiting the attack surface.

Summary

CVE-2024-8260 is an authentication bypass vulnerability (CWE-294) in the Open Policy Agent (OPA) component used in Red Hat OpenShift distributed tracing platform (Tempo) 3.4. The flaw allows an attacker with local access to the OPA CLI or its Go library functions to pass an arbitrary SMB share instead of a Rego policy file, potentially triggering SMB force-authentication. This could lead to unauthorized access or manipulation of data if exploited. The attack vector is limited due to the requirement for local access and control over OPA CLI arguments. Red Hat classifies this vulnerability as moderate severity and currently does not provide a remediation that meets their standards for deployment and stability.

CWE-294Authentication Bypass by Capture-replay (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes).
Architecture and Design
Utilize some sequence or time stamping functionality along with a checksum which takes this into account in order to ensure that messages can be parsed only once.
Architecture and Design
Since any attacker who can listen to traffic can see sequence numbers, it is necessary to sign messages with some kind of cryptography to ensure that sequence numbers are not simply doctored along with content.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Kerberoasting (opens in a new tab)
Remote Services with Stolen Credentials (opens in a new tab)
Windows Admin Shares with Stolen Credentials (opens in a new tab)
Reusing Session IDs (aka Session Replay) (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 16 Aug 2026, 17:03 UTC

WeaknessesCWE-294

Technical details

References

Community reviews

Related threats