Red Hat Security Advisory: Red Hat OpenShift distributed tracing platform (Tempo) 3.8.0 release
This release of the Red Hat OpenShift distributed tracing platform (Tempo) provides new features, security improvements, and bug fixes. Breaking changes: * Nothing Deprecations: * Nothing Technology Preview features: * Nothing Enhancements: * Nothing Bug fixes: * Before this update, the Tempo pods would stop to communicate because internal TLS certificates were renewed. With this update, the Tempo pods automatically restart when certificates are renewed. * Before this update, Tempo monolithic metrics were not being properly scraped. * https://access.redhat.com/security/cve/CVE-2025-59375 Known issues: * Nothing
AI Analysis
Technical Summary
CVE-2025-59375 is a memory amplification vulnerability in libexpat that allows attackers to trigger excessive dynamic memory allocations by submitting specially crafted XML input. This can cause the parser to allocate hundreds of megabytes of memory from a relatively small input (~250 KiB), resulting in denial-of-service through memory exhaustion. The flaw is limited to availability impact and does not enable arbitrary code execution, data leakage, or privilege escalation. Red Hat rates this vulnerability as Important (high severity) due to its potential for resource exhaustion. Mitigation strategies include input size and complexity restrictions, avoiding compressed or deeply nested XML, and using OS-level resource limits or sandboxing. The vulnerability affects multiple Red Hat products that include libexpat, including Red Hat Enterprise Linux and Red Hat OpenShift components. No explicit patch or fix version is stated in the advisory content provided.
Potential Impact
The vulnerability causes denial-of-service by allowing an attacker to cause excessive memory allocation in libexpat, leading to resource exhaustion. It impacts availability only, with no confidentiality or integrity compromise. The exploit requires submission of crafted XML input. In applications like Firefox and Thunderbird that use libexpat transitively, exploitation results in application crashes (app-level DoS). There is no known exploit in the wild reported. The impact is high severity due to potential service disruption but not critical since it does not allow code execution or data compromise.
Mitigation Recommendations
Red Hat recommends mitigating this vulnerability by limiting the size and complexity of XML inputs before parsing, avoiding compressed or deeply nested XML documents, and applying OS-level resource controls such as ulimit or setrlimit() to cap memory usage. Running the parser in a sandboxed or isolated process with strict memory and CPU limits can also help contain excessive resource consumption. No official patch or fix version is confirmed in the provided data; therefore, users should monitor Red Hat advisories for updates and apply mitigations accordingly.
Red Hat Security Advisory: Red Hat OpenShift distributed tracing platform (Tempo) 3.8.0 release
Description
This release of the Red Hat OpenShift distributed tracing platform (Tempo) provides new features, security improvements, and bug fixes. Breaking changes: * Nothing Deprecations: * Nothing Technology Preview features: * Nothing Enhancements: * Nothing Bug fixes: * Before this update, the Tempo pods would stop to communicate because internal TLS certificates were renewed. With this update, the Tempo pods automatically restart when certificates are renewed. * Before this update, Tempo monolithic metrics were not being properly scraped. * https://access.redhat.com/security/cve/CVE-2025-59375 Known issues: * Nothing
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-59375 is a memory amplification vulnerability in libexpat that allows attackers to trigger excessive dynamic memory allocations by submitting specially crafted XML input. This can cause the parser to allocate hundreds of megabytes of memory from a relatively small input (~250 KiB), resulting in denial-of-service through memory exhaustion. The flaw is limited to availability impact and does not enable arbitrary code execution, data leakage, or privilege escalation. Red Hat rates this vulnerability as Important (high severity) due to its potential for resource exhaustion. Mitigation strategies include input size and complexity restrictions, avoiding compressed or deeply nested XML, and using OS-level resource limits or sandboxing. The vulnerability affects multiple Red Hat products that include libexpat, including Red Hat Enterprise Linux and Red Hat OpenShift components. No explicit patch or fix version is stated in the advisory content provided.
Potential Impact
The vulnerability causes denial-of-service by allowing an attacker to cause excessive memory allocation in libexpat, leading to resource exhaustion. It impacts availability only, with no confidentiality or integrity compromise. The exploit requires submission of crafted XML input. In applications like Firefox and Thunderbird that use libexpat transitively, exploitation results in application crashes (app-level DoS). There is no known exploit in the wild reported. The impact is high severity due to potential service disruption but not critical since it does not allow code execution or data compromise.
Mitigation Recommendations
Red Hat recommends mitigating this vulnerability by limiting the size and complexity of XML inputs before parsing, avoiding compressed or deeply nested XML documents, and applying OS-level resource controls such as ulimit or setrlimit() to cap memory usage. Running the parser in a sandboxed or isolated process with strict memory and CPU limits can also help contain excessive resource consumption. No official patch or fix version is confirmed in the provided data; therefore, users should monitor Red Hat advisories for updates and apply mitigations accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Csaf Category
- csaf_security_advisory
- Csaf Version
- 2.0
- Publisher
- Red Hat Product Security
- Advisory Id
- RHSA-2026:5396
- Cve Count
- 1
Threat ID: 6a175eeee29bf47b50edc5d8
Added to database: 05/27/2026, 21:15:26 UTC
Last enriched: 08/16/2026, 18:09:32 UTC
Last updated: 09/14/2026, 22:01:30 UTC
Views: 54
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.