RHSA-2026:68660MediumCVSS 7.5

Red Hat Security Advisory: tomcat security, bug fix, and enhancement update

Published
September 17, 2026
Last Modified
October 23, 2026

🔗 CVE IDs covered (16)

CVE-2026-53434 →CVE-2026-55955 →CVE-2026-41293 →CVE-2026-50229 →CVE-2026-53404 →CVE-2026-59083 →CVE-2026-41284 →CVE-2026-42498 →CVE-2026-43513 →CVE-2026-43515 →CVE-2026-55276 →CVE-2026-43512 →CVE-2026-43514 →CVE-2026-55956 →CVE-2026-59084 →CVE-2026-32990 →

📋 Description

CVE-2026-32990 — Apache Tomcat: Apache Tomcat: Improper Input Validation vulnerability due to incomplete fix CVE-2026-41284 — tomcat: Apache Tomcat: Denial of Service due to uncontrolled resource allocation CVE-2026-41293 — tomcat-coyote: Apache Tomcat: HTTP/2 request headers not validated CVE-2026-42498 — tomcat-coyote: Apache Tomcat: Information disclosure due to HTTP Authentication Header exposure during WebSocket authentication. CVE-2026-43512 — tomcat-coyote: Apache Tomcat: Authentication bypass via digest authentication CVE-2026-43513 — tomcat-catalina: Apache Tomcat: Improper Handling of Case Sensitivity in LockOutRealm CVE-2026-43514 — tomcat: Apache Tomcat: Information disclosure via AJP secret timing discrepancy CVE-2026-43515 — tomcat-coyote: tomcat: Improper Authorization allows security bypass CVE-2026-50229 — tomcat: Apache Tomcat: Cross-Site Scripting vulnerability in number guess example CVE-2026-53404 — Apache Tomcat: Apache Tomcat: Incorrect control flow in rewrite valve allows unexpected rule processing CVE-2026-53434 — tomcat: Apache Tomcat: Error condition not handled when configuring CRLs CVE-2026-55276 — tomcat: Apache Tomcat: Misleading security logs due to incorrect control flow CVE-2026-55955 — tomcat: Apache Tomcat: Replay attack via improper authentication in EncryptionInterceptor CVE-2026-55956 — tomcat: Apache Tomcat: Improper Authorization Allows Security Constraint Bypass CVE-2026-59083 — tomcat: Apache Tomcat: Security constraint bypass via improper URL encoding in rewrite valve CVE-2026-59084 — tomcat: Apache Tomcat: Insufficient documentation for EncryptInterceptor may lead to insecure configurations

🎯 Affected products10

  • Red Hat Enterprise Linux AppStream (v. 9)
  • tomcat-1:9.0.120-2.el9_8.noarch as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • tomcat-1:9.0.120-2.el9_8.src as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • tomcat-admin-webapps-1:9.0.120-2.el9_8.noarch as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • tomcat-docs-webapp-1:9.0.120-2.el9_8.noarch as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • tomcat-el-3.0-api-1:9.0.120-2.el9_8.noarch as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • tomcat-jsp-2.3-api-1:9.0.120-2.el9_8.noarch as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • tomcat-lib-1:9.0.120-2.el9_8.noarch as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • tomcat-servlet-4.0-api-1:9.0.120-2.el9_8.noarch as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • tomcat-webapps-1:9.0.120-2.el9_8.noarch as a component of Red Hat Enterprise Linux AppStream (v. 9)

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 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: To mitigate this issue, disable DIGEST authentication within Apache Tomcat if it is not essential for your environment. This involves modifying the server's authentication configuration to utilize alternative methods or remove the DIGEST realm. A service restart is required for these changes to take effect and may impact functionality relying on DIGEST authentication. Workaround: This vulnerability only affects Tomcat deployments using the LockOutRealm with a case-insensitive authentication backend. Deployments not using LockOutRealm or using case-sensitive authentication backends are not affected. Workaround: Remove or disable the Tomcat example web applications if they are deployed. Example applications are not needed for production use and should not be accessible in production environments. Workaround: This vulnerability only affects Tomcat deployments that use the RewriteValve with OR-chained rewrite conditions. Deployments that do not use the RewriteValve are not affected. Review rewrite rules for OR-chained conditions and test rule evaluation behavior. Workaround: This vulnerability only affects Tomcat deployments using the FFM-based connector (requires Java 22+) with CRL-based certificate revocation checking. Deployments using the standard NIO/NIO2 connectors or not using CRL checking are not affected. Workaround: This is a logging-only issue with no runtime security impact. No mitigation is required. Administrators should not rely solely on the effective web.xml debug log output to verify security constraint configuration. Workaround: This vulnerability only affects Tomcat deployments using the EncryptionInterceptor for Tribes cluster communication. Deployments that do not use Tomcat clustering or do not configure the EncryptionInterceptor are not affected. Ensure cluster communication channels are restricted to trusted, isolated networks. Workaround: Review your application's web.xml file. Ensure security constraints explicitly deny unauthorized users by path, rather than relying strictly on filtering specific HTTP methods (like GET or POST). Workaround: To mitigate this issue, review Apache Tomcat's rewrite valve configurations. If the rewrite valve is not essential for your application, consider disabling it. If it is required, ensure its configuration does not permit improper URL encoding that could lead to security constraint bypasses. A service restart may be required for changes to take effect. Workaround: To mitigate this issue, ensure that the EncryptInterceptor in Apache Tomcat is configured according to secure best practices. Review existing configurations of EncryptInterceptor to verify that all security requirements are met and that no insecure settings are in place. If the EncryptInterceptor is not actively used, no specific action is required.

🔗 References (11)