CVE-2025-48431VulnerabilityPublished 18 Jun 2026Updated 29 Oct 2026

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

Affects Red HatSource GCVE Database

Compare

Authoritative record:CVE-2025-48431· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade Red Hat to 0.23.0 soon.

Data as of 29 Oct 2026, 09:14 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.23.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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

Upgrade Apache Thrift to 0.23.0.

Affected software

Product	Affected	Fixed in
Apache Software FoundationApache Thrift	Affected <0.23.0	Fixed in 0.23.0

Description

This release of the Red Hat OpenShift distributed tracing platform (Tempo) provides new features, security improvements, and bug fixes. Breaking changes: * None. Deprecations: * None. Technology Preview features: * None. Enhancements: * TempoStack support for the automatically injected CA bundle: The TempoStack custom resource supports the automatically injected CA bundle ca-bundle.crt for storage TLS configuration. This CA bundle is supported in addition to the service-ca.crt and ca.crt certificates. As a result, you can use the automatically injected CA bundle to simplify TLS configuration for storage for your TempoStack instances. For more information, see https://redhat.atlassian.net/browse/TRACING-6222. * Cluster TLS profile adherence: This update introduces support for cluster TLS profile adherence. The Operator uses the TLS configuration from the APIServer custom resource in all TLS communication in the Operator and its operands. As a result, you can configure the TLS cluster profile by using environment variables. For more information, see https://redhat.atlassian.net/browse/TRACING-5845. * Optional spec.size field provides predefined resource configurations: The TempoStack custom resource supports the optional spec.size field, which provides predefined, pre-tested resource configurations. The following sizes are available: 1x.demo, 1x.pico, 1x.extra-small, 1x.small, and 1x.medium. The selected size sets the resource requests and limits for the TempoStack components and a default replication factor if one is not explicitly specified. The default replication factor is 1 for 1x.demo and 2 for the other sizes. As a result, you can deploy a TempoStack instance without manually calculating resources for each component. For more information, see https://redhat.atlassian.net/browse/TRACING-5376. * Custom environment variables for TempoStack containers: The TempoStack custom resource supports the spec.env and spec.envFrom fields, which allow you to inject custom environment variables into all Tempo containers, including values sourced from a secret or config map. Combined with the spec.extraConfig field, you can reference these environment variables in the Tempo configuration by using the ${VAR_NAME} syntax. As a result, you can supply the password for a password-protected Redis cache from a secret instead of embedding it in the custom resource. For more information, see https://redhat.atlassian.net/browse/TRACING-5933. Bug fixes: * The tempo-gateway-opa container starts in namespaces that enforce a LimitRange: Before this update, the tempo-gateway-opa container was created without default resource requests and limits when percentage-based resource calculation was used. As a consequence, the container could fail to start in namespaces that enforce a LimitRange resource. With this update, the Operator sets default resource requests and limits on the tempo-gateway-opa container. As a result, the tempo-gateway-opa container starts as expected. For more information, see https://redhat.atlassian.net/browse/TRACING-5716. * TempoStack and TempoMonolithic resources no longer get stuck in a terminating state: Previously, the certificate rotation controllers in the Tempo Operator updated certificate hash annotations without checking whether a resource had a deletion timestamp. When a TempoStack or TempoMonolithic resource was deleted, these annotation updates caused resource version conflicts that prevented the foreground deletion finalizer from being removed. As a result, resources remained stuck in a terminating state. With this update, the certificate rotation controllers skip annotation updates when a resource is being deleted. As a result, TempoStack and TempoMonolithic resources are deleted correctly without getting stuck in a terminating state. For more information, see https://redhat.atlassian.net/browse/TRACING-6138. * TempoStack gateway pods spread across nodes for high availability: Previously, the TempoStack gateway deployment did not set a pod anti-affinity rule. Other components such as the distributor, querier, query front end, and ingesters did set a pod anti-affinity rule. As a result, all gateway replicas could be scheduled on the same node, reducing high availability. With this update, the gateway and compactor deployments set pod anti-affinity rules. As a result, gateway replicas are spread across nodes, which can improve high availability. For more information, see https://redhat.atlassian.net/browse/TRACING-6148. * The gateway correctly forwards OTLP HTTP traffic over HTTPS for Tempo Monolithic: Before this update, when Tempo Monolithic was configured with 'multitenancy.enabled: true' and 'ingestion.otlp.http.tls.enabled: true', the gateway forwarded OTLP HTTP traffic to the Tempo receiver using plain HTTP instead of HTTPS. As a consequence, the connection failed with a 'connection reset by peer' error because the receiver expected TLS connections. With this update, the gate

CWE-763Release of Invalid Pointer or Reference (opens in a new tab)
Base weakness
The product attempts to return a memory resource to the system, but it calls the wrong release function or calls the appropriate release function incorrectly.
Implementation
Only call matching memory management functions. Do not mix and match routines. For example, when you allocate a buffer with malloc(), dispose of the original pointer with free().
Implementation
When programming in C++, consider using smart pointers provided by the boost library to help correctly and consistently manage memory.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-1050Excessive Platform Resource Consumption within a Loop (opens in a new tab)
Base weakness
The product has a loop body or loop condition that contains a control element that directly or indirectly consumes platform resources, e.g. messaging, sessions, locks, or file descriptors.
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).
CWE-295Improper Certificate Validation (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not validate, or incorrectly validates, a certificate.
Architecture and Design · Implementation
Certificates should be carefully managed and checked to assure that data are encrypted with the intended owner's public key.
Implementation
If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
TLS Cipher String (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V9.2.1 (opens in a new tab)
V1.9.2 (opens in a new tab)
V2.8.5 (opens in a new tab)
Attack patterns
Creating a Rogue Certification Authority Certificate (opens in a new tab)
Signature Spoofing by Improper Validation (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

WeaknessesCWE-763, CWE-1050, CWE-295

Technical details

References

Community reviews

Related threats