Red Hat Security Advisory: Red Hat OpenShift distributed tracing platform (Tempo) 3.9.2 release
This release of the Red Hat OpenShift distributed tracing platform (Tempo) provides security improvements and bug fixes. Breaking changes: * None. Deprecations: * None. Technology Preview features: * None. Enhancements: * None. Bug fixes: * gRPC-Go authorization bypass vulnerability fix: Previously, gRPC-Go was vulnerable to an authorization bypass attack. This issue occurred because the HTTP/2 :path pseudo-header was not properly validated. Remote attackers could send raw HTTP/2 frames with a malformed :path that omitted the mandatory leading slash to bypass defined security policies. With this update, gRPC-Go properly validates the :path pseudo-header and rejects malformed requests. As a result, attackers can no longer bypass security policies to gain unauthorized access to services or disclose information. For more information, see https://access.redhat.com/security/cve/cve-2026-33186. * XPath component fix: Previously, the github.com/antchfx/xpath component did not properly handle certain Boolean XPath expressions. A remote attacker could submit a crafted expression that caused an infinite loop, resulting in 100% CPU utilization and a denial-of-service condition. With this update, the XPath component correctly processes Boolean expressions that evaluate to true. The system no longer enters an infinite loop when handling these expressions. For more information, see https://access.redhat.com/security/cve/cve-2026-4645. * Go JOSE denial-of-service vulnerability fix: Previously, the Go JOSE library for handling JSON Web Encryption (JWE) objects was vulnerable to a denial-of-service (DoS) attack. This issue occurred because the application failed when decrypting a specially crafted JWE object that specified a key wrapping algorithm but contained an empty encrypted key field. With this update, Go JOSE properly validates the encrypted key field before decryption. As a result, the application no longer crashes when processing malformed JWE objects, and the service remains available to legitimate users. For more information, see https://access.redhat.com/security/cve/cve-2026-34986. * Lodash _.template function fix: Previously, the lodash _.template function validated the variable option but did not validate options.imports key names. Both options passed values to the same code execution path. An attacker with the ability to control options.imports key names or pollute Object.prototype could exploit this gap to execute arbitrary code. With this update, lodash validates options.imports key names by using the same rules applied to the variable option. The _.template function rejects invalid key names and prevents code injection through this path. For more information, see https://access.redhat.com/security/cve/cve-2026-4800. * Go crypto/x509 and crypto/tls packages fix: Previously, the Go standard library crypto/x509 and crypto/tls packages did not limit the number of intermediate certificates processed during certificate chain building. An attacker could provide an excessive number of intermediate certificates, causing the system to perform an uncontrolled amount of work and resulting in a denial-of-service condition. With this update, the packages limit the number of intermediate certificates accepted during certificate chain validation. The system rejects certificate chains that exceed this limit. For more information, see https://access.redhat.com/security/cve/cve-2026-32280. * Go Root.Chmod function fix: Previously, the Root.Chmod function in the Go standard library internal/syscall/unix package had a race condition between checking and modifying a target file. An attacker could replace the target with a symbolic link after the check but before the operation completed, causing the permission change to apply to the linked file instead. This allowed an attacker to bypass directory restrictions and change permissions on unintended files. With this update, the Root.Chmod function prevents this race condition. The function no longer follows symbolic links that replace the target during execution. For more information, see https://access.redhat.com/security/cve/cve-2026-32282. * Go crypto/x509 package fix: Previously, the Go crypto/x509 package applied excluded DNS constraints to wildcard Subject Alternative Names (SANs) in a case-sensitive manner. An attacker could bypass certificate validation by using a different case in the wildcard SAN than the excluded DNS constraint specified. This allowed the system to accept a malicious certificate that should have been rejected. With this update, the package applies DNS constraints case-insensitively when validating wildcard SANs. Certificate chain verification correctly rejects certificates that match excluded DNS constraints regardless of case. For more information, see https://access.redhat.com/security/cve/cve-2026-33810. * Go crypto/tls component fix: Previously, the Go crypto/tls component did not re-validate certificates against updated certif
AI Analysis
Technical Summary
The vulnerability CVE-2025-68121 exists in the crypto/tls component and occurs during TLS session resumption if the CA settings are modified between the initial handshake and the resumed session. This flaw allows an attacker to bypass certificate validation, enabling a client or server to establish a TLS connection that should have been rejected. The issue is limited to certificate validation within the crypto/tls component and requires specific conditions to exploit, such as runtime changes to CA settings. Red Hat has released a fix in logstash-exporter-fips 1.8.4-r1 and related Red Hat OpenShift distributed tracing platform (Tempo) 3.9.2 and other affected packages. The fix ensures certificates are validated against current CA settings during session resumption, preventing the bypass.
Potential Impact
An attacker could exploit this vulnerability to bypass TLS certificate validation during session resumption, potentially allowing unauthorized connections that should be rejected. This could lead to authentication bypass scenarios under specific conditions. The vulnerability does not affect system availability and requires a controlled environment to exploit. There are no known exploits in the wild at this time.
Mitigation Recommendations
A security update addressing this vulnerability is available in logstash-exporter-fips version 1.8.4-r1 and related Red Hat products including Red Hat OpenShift distributed tracing platform (Tempo) 3.9.2. Users should apply these updates to ensure proper certificate validation during TLS session resumption. No additional mitigations are specified by the vendor. Patch status is confirmed as available.
Red Hat Security Advisory: Red Hat OpenShift distributed tracing platform (Tempo) 3.9.2 release
Description
This release of the Red Hat OpenShift distributed tracing platform (Tempo) provides security improvements and bug fixes. Breaking changes: * None. Deprecations: * None. Technology Preview features: * None. Enhancements: * None. Bug fixes: * gRPC-Go authorization bypass vulnerability fix: Previously, gRPC-Go was vulnerable to an authorization bypass attack. This issue occurred because the HTTP/2 :path pseudo-header was not properly validated. Remote attackers could send raw HTTP/2 frames with a malformed :path that omitted the mandatory leading slash to bypass defined security policies. With this update, gRPC-Go properly validates the :path pseudo-header and rejects malformed requests. As a result, attackers can no longer bypass security policies to gain unauthorized access to services or disclose information. For more information, see https://access.redhat.com/security/cve/cve-2026-33186. * XPath component fix: Previously, the github.com/antchfx/xpath component did not properly handle certain Boolean XPath expressions. A remote attacker could submit a crafted expression that caused an infinite loop, resulting in 100% CPU utilization and a denial-of-service condition. With this update, the XPath component correctly processes Boolean expressions that evaluate to true. The system no longer enters an infinite loop when handling these expressions. For more information, see https://access.redhat.com/security/cve/cve-2026-4645. * Go JOSE denial-of-service vulnerability fix: Previously, the Go JOSE library for handling JSON Web Encryption (JWE) objects was vulnerable to a denial-of-service (DoS) attack. This issue occurred because the application failed when decrypting a specially crafted JWE object that specified a key wrapping algorithm but contained an empty encrypted key field. With this update, Go JOSE properly validates the encrypted key field before decryption. As a result, the application no longer crashes when processing malformed JWE objects, and the service remains available to legitimate users. For more information, see https://access.redhat.com/security/cve/cve-2026-34986. * Lodash _.template function fix: Previously, the lodash _.template function validated the variable option but did not validate options.imports key names. Both options passed values to the same code execution path. An attacker with the ability to control options.imports key names or pollute Object.prototype could exploit this gap to execute arbitrary code. With this update, lodash validates options.imports key names by using the same rules applied to the variable option. The _.template function rejects invalid key names and prevents code injection through this path. For more information, see https://access.redhat.com/security/cve/cve-2026-4800. * Go crypto/x509 and crypto/tls packages fix: Previously, the Go standard library crypto/x509 and crypto/tls packages did not limit the number of intermediate certificates processed during certificate chain building. An attacker could provide an excessive number of intermediate certificates, causing the system to perform an uncontrolled amount of work and resulting in a denial-of-service condition. With this update, the packages limit the number of intermediate certificates accepted during certificate chain validation. The system rejects certificate chains that exceed this limit. For more information, see https://access.redhat.com/security/cve/cve-2026-32280. * Go Root.Chmod function fix: Previously, the Root.Chmod function in the Go standard library internal/syscall/unix package had a race condition between checking and modifying a target file. An attacker could replace the target with a symbolic link after the check but before the operation completed, causing the permission change to apply to the linked file instead. This allowed an attacker to bypass directory restrictions and change permissions on unintended files. With this update, the Root.Chmod function prevents this race condition. The function no longer follows symbolic links that replace the target during execution. For more information, see https://access.redhat.com/security/cve/cve-2026-32282. * Go crypto/x509 package fix: Previously, the Go crypto/x509 package applied excluded DNS constraints to wildcard Subject Alternative Names (SANs) in a case-sensitive manner. An attacker could bypass certificate validation by using a different case in the wildcard SAN than the excluded DNS constraint specified. This allowed the system to accept a malicious certificate that should have been rejected. With this update, the package applies DNS constraints case-insensitively when validating wildcard SANs. Certificate chain verification correctly rejects certificates that match excluded DNS constraints regardless of case. For more information, see https://access.redhat.com/security/cve/cve-2026-33810. * Go crypto/tls component fix: Previously, the Go crypto/tls component did not re-validate certificates against updated certif
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability CVE-2025-68121 exists in the crypto/tls component and occurs during TLS session resumption if the CA settings are modified between the initial handshake and the resumed session. This flaw allows an attacker to bypass certificate validation, enabling a client or server to establish a TLS connection that should have been rejected. The issue is limited to certificate validation within the crypto/tls component and requires specific conditions to exploit, such as runtime changes to CA settings. Red Hat has released a fix in logstash-exporter-fips 1.8.4-r1 and related Red Hat OpenShift distributed tracing platform (Tempo) 3.9.2 and other affected packages. The fix ensures certificates are validated against current CA settings during session resumption, preventing the bypass.
Potential Impact
An attacker could exploit this vulnerability to bypass TLS certificate validation during session resumption, potentially allowing unauthorized connections that should be rejected. This could lead to authentication bypass scenarios under specific conditions. The vulnerability does not affect system availability and requires a controlled environment to exploit. There are no known exploits in the wild at this time.
Mitigation Recommendations
A security update addressing this vulnerability is available in logstash-exporter-fips version 1.8.4-r1 and related Red Hat products including Red Hat OpenShift distributed tracing platform (Tempo) 3.9.2. Users should apply these updates to ensure proper certificate validation during TLS session resumption. No additional mitigations are specified by the vendor. Patch status is confirmed as available.
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:9385
- Cve Count
- 12
- Additional Cves
- ["CVE-2026-4645","CVE-2026-4800","CVE-2026-4926","CVE-2026-25679","CVE-2026-27137","CVE-2026-32280","CVE-2026-32282","CVE-2026-32285","CVE-2026-33186","CVE-2026-33810","CVE-2026-34986"]
- State
- PUBLISHED
Threat ID: 6a160952e29bf47b50618c9a
Added to database: 05/26/2026, 20:57:54 UTC
Last enriched: 08/15/2026, 00:26:41 UTC
Last updated: 09/14/2026, 22:01:30 UTC
Views: 220
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.