RHSA-2026:6569HighCVSS 7.5

Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update

Published
April 4, 2026
Last Modified
September 6, 2026

🔗 CVE IDs covered (7)

CVE-2026-24733 →CVE-2026-24734 →CVE-2025-55668 →CVE-2025-55752 →CVE-2025-55754 →CVE-2025-61795 →CVE-2025-66614 →

📋 Description

CVE-2025-55668 — org.apache.tomcat/tomcat-catalina: tomcat: Apache Tomcat: session fixation via rewrite valve CVE-2025-55752 — tomcat: org.apache.tomcat/tomcat-catalina: Apache Tomcat: Directory traversal via rewrite with possible RCE CVE-2025-55754 — org.apache.tomcat/tomcat-juli: tomcat: Apache Tomcat: console manipulation CVE-2025-61795 — tomcat: org.apache.tomcat/tomcat-catalina: Apache Tomcat: Denial of service CVE-2025-66614 — tomcat: Client certificate verification bypass due to virtual host mapping CVE-2026-24733 — tomcat: security constraint bypass with HTTP/0.9 CVE-2026-24734 — tomcat: Apache Tomcat: Certificate revocation bypass due to improper OCSP response validation

🎯 Affected products3

  • Red Hat Hardened Images
  • tomcat11-main@noarch as a component of Red Hat Hardened Images
  • tomcat11-main@src as a component of Red Hat Hardened Images

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. To reduced the risk, by disabling or strictly limiting the use of HTTP PUT requests to trusted, authenticated users only. Additionally, administrators should review and adjust URL rewrite rules to ensure they do not manipulate request paths in ways that could expose protected directories such as /WEB-INF/ or /META-INF/. Implementing strict access controls and monitoring for unexpected rewrite or upload behavior can further minimize potential exploitation. Workaround: To mitigate this vulnerability, ensure that security constraints are consistent across similar methods (e.g., if GET is denied, HEAD should likely be denied) or block HTTP/0.9 traffic via a reverse proxy or firewall, if it is not required.

🔗 References (11)