Quick answers
- Is CVE-2026-111250 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111250 being exploited in the wild.
- How severe is CVE-2026-111250?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Apache OpenEJB.
- Is there a fix for CVE-2026-111250?
- 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. 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-111250 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-111250?
- 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.
Technical details
The vulnerability is an authentication bypass in OpenEJB's embedded HTTP server when applications rely on programmatic authentication. An unauthenticated remote attacker can bypass authentication checks by making HTTP requests, gaining access to protected functionality. The issue affects only applications served by the embedded HTTP server that implement authentication programmatically rather than through container-managed security.
Affected products
- Apache OpenEJB
Timeline
- 2026-11-10: disclosed