CVE-2026-111263: Apache TomEE: Missing authentication on EJB web service endpoints deployed in a web application

Q: Which deployments are exposed to unauthenticated remote access?

EJB JAX-WS endpoints are exposed when they are published within an existing web application and rely on authentication configured only in the TomEE deployment descriptor. They are not exposed in this way if the application independently protects the endpoint with web.xml security constraints or EJB method permissions.

Q: What does an attacker need to exploit this issue?

An attacker only needs remote access to the affected web service endpoint. No authentication is required when the affected deployment pattern is used without application-level protections.

Q: What can be done if an upgrade cannot be applied immediately?

Protect the endpoint at the application level by adding web.xml security constraints or EJB method permissions. These controls prevent the unauthenticated invocation described in the advisory.

Q: Which versions contain the fix?

The issue is fixed in Apache TomEE 10.3.0 and 11.0.0-M2.

Published Nov 10, 2026

Updated

Authentication configured for an EJB JAX-WS endpoint in the TomEE deployment descriptor is not enforced when the endpoint is published within an existing web application. A remote unauthenticated attacker can invoke the web service operations, unless the application protects the endpoint with its own web.xml security constraints or EJB method permissions. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.

Affected Software

1 affected component

Apache TomEE<10.3.0, <11.0.0-M2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade Apache TomEE to a version that resolves this vulnerability.
Fixed in 10.3.0
Upgrade
Upgrade Apache TomEE to a version that resolves this vulnerability.
Fixed in 11.0.0-M2

Event History

Nov 10, 2026

CVE Published

via MITRE·03:05 PM

Data Sourced

via MITRE·03:05 PM

DescriptionWeakness

Data Sourced

via NVD·03:17 PM

DescriptionWeakness

Frequently Asked Questions

Which deployments are exposed to unauthenticated remote access?

EJB JAX-WS endpoints are exposed when they are published within an existing web application and rely on authentication configured only in the TomEE deployment descriptor. They are not exposed in this way if the application independently protects the endpoint with web.xml security constraints or EJB method permissions.

What does an attacker need to exploit this issue?

An attacker only needs remote access to the affected web service endpoint. No authentication is required when the affected deployment pattern is used without application-level protections.

What can be done if an upgrade cannot be applied immediately?

Protect the endpoint at the application level by adding web.xml security constraints or EJB method permissions. These controls prevent the unauthenticated invocation described in the advisory.

Which versions contain the fix?

The issue is fixed in Apache TomEE 10.3.0 and 11.0.0-M2.

CVE-2026-111263: Apache TomEE: Missing authentication on EJB web service endpoints deployed in a web application

Affected Software

Remediation

Event History

Frequently Asked Questions

Which deployments are exposed to unauthenticated remote access?

What does an attacker need to exploit this issue?

What can be done if an upgrade cannot be applied immediately?

Which versions contain the fix?

Company

Resources

Contact

Frequently Asked Questions

Which deployments are exposed to unauthenticated remote access?

What does an attacker need to exploit this issue?

What can be done if an upgrade cannot be applied immediately?

Which versions contain the fix?