RHSA-2026:67163HighCVSS 7.3

Red Hat Security Advisory: tomcat9 security update

Published
September 14, 2026
Last Modified
September 14, 2026

🔗 CVE IDs covered (9)

CVE-2026-41293 →CVE-2026-42498 →CVE-2026-43512 →CVE-2026-43513 →CVE-2026-43515 →CVE-2026-59084 →CVE-2026-32990 →CVE-2026-55957 →CVE-2026-59083 →

📋 Description

CVE-2026-32990 — Apache Tomcat: Apache Tomcat: Improper Input Validation vulnerability due to incomplete fix 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-43515 — tomcat-coyote: tomcat: Improper Authorization allows security bypass CVE-2026-55957 — tomcat: Apache Tomcat: Authentication bypass via missing critical step in JNDIRealm GSSAPI configuration 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 EUS (v. 10.0)
  • tomcat9-1:9.0.120-1.el10_0.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • tomcat9-1:9.0.120-1.el10_0.src as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • tomcat9-admin-webapps-1:9.0.120-1.el10_0.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • tomcat9-docs-webapp-1:9.0.120-1.el10_0.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • tomcat9-el-3.0-api-1:9.0.120-1.el10_0.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • tomcat9-jsp-2.3-api-1:9.0.120-1.el10_0.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • tomcat9-lib-1:9.0.120-1.el10_0.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • tomcat9-servlet-4.0-api-1:9.0.120-1.el10_0.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • tomcat9-webapps-1:9.0.120-1.el10_0.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)

✅ 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: Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible. 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 (12)