Skip to content
Fencer Intel
medium —

CVE-2026-111245 json

Apache TomEE: Privilege escalation via WS-Security caller identity leaking between requests

published yesterday modified yesterday also EUVD-2026-121245

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 13%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.apache.tomee:openejb-cxf 10.0.0-M1, 10.3.0, 11.0.0-M2
  • Apache Software Foundation Apache TomEE 10.0.0-M1, 10.3.0, 11.0.0-M2

Is CVE-2026-111245 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-11).

Affected packages

ecosystem package affected fixed in
maven org.apache.openejb:openejb-cxf
>=4.0.0-beta-1, <=4.7.5
 no fix listed
maven org.apache.tomee:openejb-cxf
>=7.0.0-M1, <10.0.0-M1
>=10.0.0-M1, <10.3.0
>=11.0.0-M1, <11.0.0-M2
10.0.0-M1
10.3.0
11.0.0-M2

Affected products

  • Apache Software Foundation Apache TomEE

Classification

Weakness
  • CWE-488 Exposure of Data Element to Wrong Session

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.