# CVE-2026-111248: Apache Tomcat Jakarta Security credential handler bypass

Source: https://junglewise.ai/threats/cve-2026-111248-the-jakarta-security-identity-store-backed-by-the-tomcat-user  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-111248 · Severity: info · Published 2026-11-10

Apache Tomcat's Jakarta Security identity store compares supplied passwords against stored digests as plain text, bypassing the configured password hashing mechanism. An attacker with access to a leaked or backed-up user database can authenticate using the stored digest value directly without knowing the actual password, gaining unauthorized access to web applications.

Technologies: [Apache Tomcat](https://junglewise.ai/threats/technologies/tomcat). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## 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

## References

- [https://repo.maven.apache.org/maven2](https://repo.maven.apache.org/maven2)
- [https://lists.apache.org/thread/47svr3bg4lchzlhkl55g5bfykhnx48jo](https://lists.apache.org/thread/47svr3bg4lchzlhkl55g5bfykhnx48jo)

## Related threats

- [Apache Tomcat incomplete cleanup in TLS 1.3 connections](https://junglewise.ai/threats/cve-2026-93446-incomplete-cleanup-vulnerability-in-apache-tomcat-could-cause-tls)
- [Apache Tomcat HTTP trailer information leak between requests](https://junglewise.ai/threats/cve-2026-88041-incomplete-cleanup-vulnerability-in-apache-tomcat-allowed-an)
- [Apache Tomcat TOCTOU race condition in APR/Native connector](https://junglewise.ai/threats/cve-2026-80353-time-of-check-time-of-use-toctou-race-condition-vulnerability-in)
- [Apache Tomcat Execution After Redirect vulnerability](https://junglewise.ai/threats/cve-2026-74049-execution-after-redirect-ear-vulnerability-in-apache-tomcat-this)
- [Apache Tomcat FIPS mode validation not failing securely](https://junglewise.ai/threats/cve-2026-74048-not-failing-securely-failing-open-vulnerability-in-apache-tomcat)