External risk intelligence

OpenEJB Embedded HTTP Server Authentication Bypass

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-111256

The vulnerability affects JAX-WS and JAX-RS endpoints, which are commonly used to build web services and APIs. These components are frequently deployed as internet-facing or edge services. Because the flaw involves an embedded HTTP server exposing these endpoints without authentication, it directly impacts the accessibility of service interfaces that are often intended for network or public consumption.

Missing Authentication

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 vulnerability affects Java endpoints, specifically those published by an embedded HTTP server rather than a more common one like Tomcat. When configured incorrectly, these endpoints can be accessed by anyone on the network without needing a password. The main concern is confirming if your systems use this specific embedded server and are exposed to untrusted users.

  • Unauthenticated access to Java services.
  • Affects systems using embedded HTTP servers.
  • Confirm relevance and exposure to untrusted clients.

Attack Path

How an attacker could exploit the issue

An attacker can reach JAX-WS or JAX-RS endpoints that are published by the embedded OpenEJB HTTP server. If these endpoints are configured to use authentication but the embedded server silently ignores it, the attacker can invoke the exposed operations without needing any credentials. This can lead to unauthorized access and control over the application's functionalities, especially in deployments that rely on this specific embedded server setup.

  • Remote unauthenticated access required.
  • Authentication methods are ignored.
  • Unauthorized access to exposed operations.

Live Threat

Current exploitation, exposure, and threat context

When JAX-WS or JAX-RS endpoints are published using the embedded OpenEJB HTTP server instead of Tomcat, certain authentication methods may be ignored, allowing unauthenticated remote attackers to invoke exposed operations. This impacts deployments that specifically use the embedded HTTP server and rely on the affected authentication methods.

  • Service endpoints and operations.
  • Invoked remotely without credentials.
  • Unauthorized access to service functions.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability affects JAX-WS or JAX-RS endpoints published by an embedded OpenEJB HTTP server, potentially exposing them without authentication. Application owners or platform teams responsible for these endpoints should prioritize identifying affected systems, assessing their exposure and business criticality, and coordinating remediation.

  • Identify affected JAX-WS/JAX-RS endpoints.
  • Verify network reachability and business criticality.
  • Plan remediation or implement network blocks.

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 the role of the OpenEJB embedded HTTP server in Java applications?

It serves as a lightweight component within the OpenEJB container to host JAX-WS and JAX-RS service endpoints. Unlike Tomcat, which is a full-featured web server, this embedded alternative is often utilized for streamlined testing or rapid service delivery, functioning as the transport layer for API communications directly within the application's runtime environment.

How does CVE-2026-111256 manifest as a security weakness?

This vulnerability is classified as CWE-306, Missing Authentication for Critical Function. It occurs because the embedded server fails to enforce configured authentication mechanisms for JAX-WS or JAX-RS endpoints, causing them to be exposed publicly without credential validation.

Can authentication be bypassed if my application uses Tomcat?

No. The security flaw is specific to the embedded OpenEJB HTTP server implementation. Deployments that utilize Tomcat to manage or publish their JAX-WS and JAX-RS endpoints do not trigger this authentication bypass, as the problematic code path is unique to the embedded server logic.

Why is this vulnerability considered a relevant threat to my service infrastructure?

According to the Halo Surface Signal, this flaw is highly relevant because JAX-WS and JAX-RS endpoints are commonly internet-facing. Because the issue allows unauthenticated access to these service interfaces, it poses a direct risk to edge services that manage sensitive data or administrative functions.

How should teams secure systems against this authentication flaw?

Prioritize identifying all endpoints utilizing the embedded OpenEJB server. For immediate risk reduction, block network access to these services from untrusted sources. Long-term remediation involves migrating these service deployments to a Tomcat-based environment, such as TomEE, which correctly handles authentication requirements.

References