CVE-2026-111248 · Runtime
NO FIX YET · SEE WHAT TO DO
Tomcat's Jakarta Security identity store, when backed by the Tomcat user database, compares logins as plain text and skips the configured credential handler. An attacker who obtains a stored password digest, such as from a leaked users file or backup, can log in with that digest instead of the real password.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Applications running on Apache Tomcat that use Jakarta Security with the Tomcat user database as the identity store, and store passwords as digests. Deployments using other identity stores, plain-text passwords, or no Jakarta Security integration are not exposed by this description.
Not affected if no-jakarta-security, other-identity-store, plain-text-passwords
Who cares jakarta-ee, java, self-hosted, tomcat
catalina.sh version and compare it to the fixed versions below.10.3.0.11.0.0-M2.The Jakarta Security identity store backed by the Tomcat user database compares the supplied password with the stored value as plain text and ignores the configured credential handler. When digested passwords are stored, an attacker who obtained a stored digest, for example from a leaked users file or backup, can authenticate with the digest instead of the password. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.