Quick answers
- Is CVE-2026-111248 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111248 being exploited in the wild.
- How severe is CVE-2026-111248?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Apache Tomcat before 10.3.0, before 11.0.0-M2.
- Is there a fix for CVE-2026-111248?
- Yes: fixed in Tomcat 10.3.0, 11.0.0-M2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111248 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-111248?
- Check whether you run Apache Tomcat at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Tomcat 10.3.0, 11.0.0-M2
Technical details
The vulnerability occurs in the identity store implementation backed by Tomcat's user database, where password comparison ignores the configured credential handler and performs plain-text matching. This allows an attacker who obtains a password digest (e.g., from a leaked users file) to authenticate by supplying the digest itself instead of the plaintext password. The issue affects Tomcat versions before 10.3.0 and 11.0.0-M2.
Affected products
- Apache Tomcat before 10.3.0, before 11.0.0-M2