CVE-2026-111242: Apache TomEE · Exposure of Data Element to Wrong Session
Affects Apache TomEESource CVE Database V5
Not known to be exploited · fixed in 11.0.0-M2 : patch Apache TomEE soon.
Data as of 10 Nov 2026, 15:50 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 11.0.0-M2, 10.3.0, 10.0.0-M1
Exploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade Apache TomEE and org.apache.tomee/mp-jwt to 11.0.0-M2, 10.3.0 or 10.0.0-M1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache TomEEorg.apache.tomee:mp-jwt | Affected
| Fixed in
|
| Apache TomEEorg.apache.tomee:mp-jwt | Affected
| Fixed in
|
| Apache TomEEorg.apache.tomee:mp-jwt | Affected
| Fixed in
|
Mavenorg.apache.tomee/mp-jwtpkg:maven/org.apache.tomee/mp-jwtOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade Apache TomEE to version 10.3.0 or 11.0.0-M2, where this vulnerability is fixed. No other mitigation or temporary workaround is indicated in the advisory.
Description
Apache TomEE versions prior to 10.3.0 and 11.0.0-M2 have a vulnerability in MicroProfile JWT authentication where the security state for a request is not always cleared from the processing thread if the request does not complete normally. This can allow a remote attacker with a valid token to cause unrelated requests on the same thread to execute with elevated run-as identity privileges. Upgrading to versions 10.3.0 or 11.0.0-M2 mitigates this issue.