Quick answers
- Is CVE-2026-111245 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111245 being exploited in the wild.
- How severe is CVE-2026-111245?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Apache OpenEJB versions prior to 10.3.0 and 11.0.0-M2.
- Is there a fix for CVE-2026-111245?
- Yes: fixed in Apache OpenEJB 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-111245 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-111245?
- Check whether you run Apache OpenEJB 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: Apache OpenEJB 10.3.0, 11.0.0-M2
Technical details
When WS-Security UsernameToken authentication succeeds in OpenEJB's HTTP server, the caller identity remains bound to the worker thread after the request completes. A subsequent unauthenticated request routed to the same thread can invoke protected EJB methods using the stale authentication context from the previous request. This is a thread-safety issue in session/identity cleanup that requires no additional authentication from the attacker.
Affected products
- Apache OpenEJB versions prior to 10.3.0 and 11.0.0-M2
Timeline
- 2026-11-10: disclosed