# CVE-2026-86336: Apache TomEE EJB authorization bypass on JDK 21+

Source: https://junglewise.ai/threats/cve-2026-86336-apache-tomee-running-on-jdk-21-or-later-skips-ejb-method  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-86336 · Severity: info · Published 2026-11-10

Apache TomEE, an application server that runs Java enterprise applications, skips security checks on EJB (Enterprise JavaBeans) method calls when running on JDK 21 or later. This allows attackers to invoke protected EJB methods that should be restricted, potentially accessing or modifying sensitive business logic and data without proper authentication or authorization.

Technologies: [Apache TomEE](https://junglewise.ai/threats/technologies/tomee). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## Quick answers

**Is CVE-2026-86336 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-86336 being exploited in the wild.

**How severe is CVE-2026-86336?** Informational severity, published 10 November 2026.

**Which products and versions are affected?** Apache TomEE all versions on JDK 21+.

**Is there a fix for CVE-2026-86336?** Yes: fixed in TomEE 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-86336 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-86336?** Check whether you run Apache TomEE 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 TomEE 10.3.0, 11.0.0-M2

## Technical details

The vulnerability is an authorization bypass in EJB method access control that occurs specifically on JDK 21 and later. Callers can invoke EJB methods that have configured access restrictions without those restrictions being enforced, likely due to compatibility issues with newer Java versions. The attack requires network access to the TomEE instance and knowledge of the EJB methods to target.

## Affected products

- Apache TomEE all versions on JDK 21+

## Timeline

- 2026-11-10: disclosed

## References

- [https://repo.maven.apache.org/maven2](https://repo.maven.apache.org/maven2)
- [https://lists.apache.org/thread/tv0407xmnpy4qctqm9nzx56lgjln2t4j](https://lists.apache.org/thread/tv0407xmnpy4qctqm9nzx56lgjln2t4j)

## Related threats

- [Apache TomEE default administrative user authentication bypass](https://junglewise.ai/threats/cve-2026-111257-with-the-default-configuration-and-no-users-defined-in-the)
- [Apache TomEE authentication bypass in JAX-WS endpoint](https://junglewise.ai/threats/cve-2026-111263-authentication-configured-for-an-ejb-jax-ws-endpoint-in-the)