CVE-2026-116561
Patch Available.
This Vulnerability has been fixed in the Never-Ending Support (NES) version offered by HeroDevs.
Overview
Apache Tomcat is an open-source implementation of the Jakarta Servlet, Jakarta Pages, Jakarta Expression Language, Jakarta WebSocket, Jakarta Annotations, and Jakarta Authentication specifications. It serves Java web applications either as a standalone servlet container and HTTP server or embedded inside an application through the tomcat-embed-core artifact. Its Catalina servlet container (org.apache.tomcat:tomcat-catalina) supplies the request-processing pipeline, including Valves such as RewriteValve, along with connectors, realms, and session management.
An information exposure vulnerability (CVE-2026-116561) has been identified in the Jakarta Authentication (JASPIC) support of the Apache Tomcat authenticators, which allows a response to be sent to the client as a successful HTTP 200 response even though the configured authentication module failed to secure it. When the module's secureResponse() call throws an AuthException, Tomcat logs a warning and delivers the response without the protection the module was meant to apply, instead of returning an HTTP 500 error.
Per OWASP: Access control enforces policy such that users cannot act outside of their intended permissions. Failures typically lead to unauthorized information disclosure, modification, or destruction of all data or performing a business function outside the user's limits.
This issue affects multiple versions of Apache Tomcat, including the End-of-Life 8.5.x line.
Details
Module Info
- Product: Apache Tomcat
- Affected packages:
org.apache.tomcat:tomcat-catalina,org.apache.tomcat.embed:tomcat-embed-core - Affected versions: >=8.5.0 <=8.5.100, >=9.0.0.M1 <=9.0.123, >=10.1.0-M1 <=10.1.61, >=11.0.0-M1 <=11.0.27
- GitHub repository: https://github.com/apache/tomcat
- Published packages: https://central.sonatype.com/artifact/org.apache.tomcat/tomcat-catalina, https://central.sonatype.com/artifact/org.apache.tomcat.embed/tomcat-embed-core
- Package manager: Maven
- Fixed in:
- OSS Apache Tomcat 9.0.124, 10.1.62, 11.0.29
- NES for Apache Tomcat v8.5.116
Vulnerability Info
This Low-severity vulnerability is found in the org.apache.tomcat:tomcat-catalina and org.apache.tomcat.embed:tomcat-embed-core packages in multiple versions of Apache Tomcat. When a Jakarta Authentication (JASPIC) provider is registered for an application, AuthenticatorBase hands each response to the provider's ServerAuthContext.secureResponse() before it is sent, so the authentication module can apply its response-side protection. The specification requires a failure at this step to end in an error response. In AuthenticatorBase, the helper that performs this call catches the AuthException, logs a warning and returns normally:
private void secureResponseJspic(Request request, Response response, JaspicState state) {
try {
state.serverAuthContext.secureResponse(state.messageInfo, null);
request.setRequest((HttpServletRequest) state.messageInfo.getRequestMessage());
response.setResponse((HttpServletResponse) state.messageInfo.getResponseMessage());
} catch (AuthException e) {
log.warn(sm.getString("authenticator.jaspicSecureResponseFail"), e);
}
}
The helper is called from invoke() after the rest of the pipeline has produced the response, and from authenticate(), which returns the result of authenticateJaspic() without regard to whether the response could be secured:
boolean result = authenticateJaspic(request, response, jaspicState, true);
secureResponseJspic(request, response, jaspicState);
return result;
Because the exception is swallowed, the response status is never changed and authenticate() still reports success. The application's response, which the authentication module failed to secure, is therefore committed to the client as a normal HTTP 200 response rather than an HTTP 500 error.
Mitigation
Only recent versions of Apache Tomcat are community-supported. The community support version will not receive any updates to address this issue. For more information, see here.
Users of the affected components should apply one of the following mitigations:
- Upgrade to a patched version of Apache Tomcat.
- Leverage a commercial support partner like HeroDevs for post-EOL security support.
Credits
- Moritz Theile (finder)