Quick answers
- Is CVE-2026-97881 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-97881 being exploited in the wild.
- How severe is CVE-2026-97881?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Apache OpenEJB.
- Is there a fix for CVE-2026-97881?
- 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 limitation. 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-97881 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-97881?
- 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 limitation.
Technical details
The vulnerability is a path traversal flaw in the embedded OpenEJB HTTP server's static resource handler. The server fails to restrict resource requests to configured directories, allowing an attacker to use relative path sequences to read files outside intended boundaries. No authentication is required; the attack is network-accessible and exploitable by sending crafted HTTP requests.
Affected products
- Apache OpenEJB
Timeline
- 2026-11-10: disclosed