Quick answers
- Is CVE-2026-86531 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86531 being exploited in the wild.
- How severe is CVE-2026-86531?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Apache OpenEJB <unknown>.
- Is there a fix for CVE-2026-86531?
- No fixed version is recorded yet. Block network access to the embedded OpenEJB HTTP server from untrusted clients, or migrate to Tomcat-based TomEE distributions which are not affected. 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-86531 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-86531?
- 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
Block network access to the embedded OpenEJB HTTP server from untrusted clients, or migrate to Tomcat-based TomEE distributions which are not affected.
Technical details
The OpenEJB embedded HTTP server lacks input size limits on request bodies and multipart form data, and does not remove temporary files created during multipart request handling. An unauthenticated remote attacker can exploit this via network access to trigger denial of service through resource exhaustion (memory or disk). The vulnerability does not affect Tomcat-based TomEE deployments.
Affected products
- Apache OpenEJB <unknown>
Timeline
- 2026-11-10: disclosed