External risk intelligence

Apache TomEE EJB Authorization Bypass Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-86336

Apache TomEE is a Java EE application server commonly deployed to host web applications and APIs that are exposed to the internet. Since the vulnerability affects EJB method authorization, applications using EJB services directly exposed via web or remote interfaces are commonly reachable in typical deployments.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a vulnerability in Apache TomEE, a Java enterprise application server. The issue allows unauthorized callers to bypass access controls on certain methods, potentially exposing business logic and data. The main concern is confirming relevance and exposure to our specific deployments.

  • Bypasses authorization checks on methods.
  • Affects how application access controls function.
  • Verify usage and potential impact on our services.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this by directly calling Enterprise JavaBeans (EJB) methods on an affected Apache TomEE server. Because the server fails to check the caller's permissions, any unauthenticated user on the network could invoke methods that are normally restricted, potentially leading to unauthorized access to sensitive data or functionality.

  • No authentication required.
  • Directly invoke EJB methods.
  • Unauthorized access to functionality.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, Apache TomEE running on JDK 21 or later could allow callers to invoke Enterprise JavaBeans (EJB) methods without proper access restrictions being enforced. This could affect the intended behavior of EJB services by bypassing configured authorization checks.

  • EJB method authorization.
  • Invoking methods without checks.
  • Unauthorized access to EJB functionality.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Apache TomEE may require action from application owners, platform teams, and potentially security teams responsible for the underlying JDK. The first practical step is to inventory all TomEE instances, confirm their network exposure and criticality, and identify the accountable owner for each instance. Subsequently, a remediation plan should be developed based on the identified risk.

  • Application and platform teams own remediation.
  • Verify TomEE instances and network exposure.
  • Plan and coordinate controlled upgrades.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Apache TomEE?

Apache TomEE is a lightweight, open-source enterprise Java application server. It extends Apache Tomcat by adding capabilities to run Java EE (Enterprise Edition) applications, such as Enterprise JavaBeans (EJB). Developers use it to build and host robust web applications and services that require complex business logic, resource management, and secure component communication.

What does CVE-2026-86336 mean for EJB security?

This vulnerability involves a flaw in how the software handles security constraints, categorized as CWE-862: Missing Authorization. In this specific case, the server fails to verify if a caller has the necessary permissions to execute specific EJB methods. Consequently, the access controls that developers configured to protect sensitive business logic or data are ignored, allowing unauthorized execution of those functions.

How does an attacker trigger this vulnerability?

An attacker triggers this by directly invoking restricted EJB methods on an affected server. The precondition for this bypass is that the Apache TomEE instance must be running on JDK 21 or later. Simply accessing the server is not enough; the attacker must specifically target the EJB interface. Installations running on older versions of the Java Development Kit (pre-JDK 21) are not subject to this specific authorization failure.

Why should I care about this CVE-2026-86336?

According to Halo Surface Signal, Apache TomEE is frequently deployed to host web applications and APIs directly reachable from the internet. Because this flaw allows for the bypass of critical method-level security, any EJB service exposed through web or remote interfaces is at significant risk. You should prioritize this if your infrastructure hosts externally facing Java enterprise applications that rely on EJB for internal logic or data access.

Do I need to update my Apache TomEE environment?

Yes. If you are running Apache TomEE on JDK 21 or later, you should coordinate with your application and platform teams to perform an upgrade. The project maintainers have provided versions 10.3.0 and 11.0.0-M2 to resolve this authorization bypass. Start by inventorying all your TomEE instances to determine which are affected and planning a controlled update process.

References