# CVE-2026-111263: Apache TomEE authentication bypass in JAX-WS endpoint

Source: https://junglewise.ai/threats/cve-2026-111263-authentication-configured-for-an-ejb-jax-ws-endpoint-in-the  
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-111263 · Severity: info · Published 2026-11-10

Apache TomEE is a Java application server that runs enterprise web applications. When a web service endpoint is published within an existing application, authentication rules configured in the deployment descriptor are not enforced, allowing unauthenticated attackers to invoke protected operations. An attacker can access sensitive web service functionality without valid credentials if the application does not add separate security controls.

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

## Quick answers

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

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

**Which products and versions are affected?** Apache TomEE prior to 10.3.0 and 11.0.0-M2.

**Is there a fix for CVE-2026-111263?** Yes: fixed in TomEE 10.3.0, 11.0.0-M2. Until then: Protect JAX-WS endpoints with additional security constraints defined in the application's own web.xml or by implementing EJB method permissions at the bean level. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-111263 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-111263?** 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

Protect JAX-WS endpoints with additional security constraints defined in the application's own web.xml or by implementing EJB method permissions at the bean level.

## Technical details

The vulnerability is an authentication bypass in EJB JAX-WS endpoints published within an existing web application context in TomEE. The deployment descriptor's authentication configuration is not enforced at the web service level, though a workaround exists if the application implements its own web.xml security constraints or EJB method permissions. Remote unauthenticated attackers can invoke web service operations without authentication.

## Affected products

- Apache TomEE prior to 10.3.0 and 11.0.0-M2

## Timeline

- 2026-11-10: disclosed

## References

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

## Related threats

- [Apache TomEE EJB authorization bypass on JDK 21+](https://junglewise.ai/threats/cve-2026-86336-apache-tomee-running-on-jdk-21-or-later-skips-ejb-method)
- [Apache TomEE default administrative user authentication bypass](https://junglewise.ai/threats/cve-2026-111257-with-the-default-configuration-and-no-users-defined-in-the)