Quick answers
- Is CVE-2026-97888 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-97888 being exploited in the wild.
- How severe is CVE-2026-97888?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Apache OpenEJB.
- Is there a fix for CVE-2026-97888?
- No fixed version is recorded yet. Block network access to the embedded HTTP server from untrusted clients, or migrate to the Tomcat-based TomEE distributions which do not have this vulnerability. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-97888 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-97888?
- Check whether you run Apache OpenEJB. 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
Block network access to the embedded HTTP server from untrusted clients, or migrate to the Tomcat-based TomEE distributions which do not have this vulnerability.
Technical details
The embedded HTTP server in Apache OpenEJB does not clear the security identity context after processing an authenticated request before reusing the worker thread for the next request. An unauthenticated remote attacker can craft a request following an authenticated user's request on the same thread, causing their request to execute with the previous user's privileges. Only applications using programmatic or HTTP basic authentication are affected.
Affected products
- Apache OpenEJB
Timeline
- 2026-11-10: disclosed