After a successful WS-Security UsernameToken authentication, the caller identity stays associated with the worker thread once the request completes when web services are served by the standalone OpenEJB HTTP server
Source GCVE Database
Not known to be exploited · fixed in 11.0.0-M2 : patch Apache TomEE soon.
Data as of 10 Nov 2026, 19:05 UTC
Rated by Threat Radar · 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/openejb-cxf to 11.0.0-M2, 10.3.0 or 10.0.0-M1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache TomEEorg.apache.openejb:openejb-cxf | Affected
| Fixed in– |
| Apache TomEEorg.apache.tomee:openejb-cxf | Affected
| Fixed in
|
| Apache TomEEorg.apache.tomee:openejb-cxf | Affected
| Fixed in
|
| Apache TomEEorg.apache.tomee:openejb-cxf | Affected
| Fixed in
|
Mavenorg.apache.openejb/openejb-cxfpkg:maven/org.apache.openejb/openejb-cxfOther threats | Affected
| Fixed in– |
Mavenorg.apache.tomee/openejb-cxfpkg:maven/org.apache.tomee/openejb-cxfOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
After a successful WS-Security UsernameToken authentication, the caller identity stays associated with the worker thread once the request completes when web services are served by the standalone OpenEJB HTTP server. A remote unauthenticated attacker whose request is later processed on the same thread can invoke protected EJB methods with the identity of a previously authenticated user. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.