External risk intelligence

EJB JAX-WS Endpoint Authentication Bypass Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-111264

The vulnerability affects EJB JAX-WS endpoints, which are commonly deployed as web service or API endpoints. Since these services are often exposed to the network to facilitate communication between distributed systems or as public-facing APIs, they are frequently reachable from the internet, making them a common part of an organization's public-facing attack surface.

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

A critical vulnerability has been identified in EJB JAX-WS endpoints, potentially allowing unauthenticated remote attackers to bypass security controls. This issue affects how certain web service and API endpoints authenticate requests, posing a risk if these services are accessible over the network. The primary concern is to confirm if your organization utilizes this technology and is exposed.

  • Authentication bypass on web service endpoints.
  • Confirms relevance and exposure for leadership.
  • Understand and confirm potential exposure to business.

Attack Path

How an attacker could exploit the issue

An attacker can bypass authentication on EJB JAX-WS endpoints by sending requests with an unsupported HTTP method, allowing them to access protected resources. This bypass could lead to unauthorized data access, modification, or system disruption.

  • Unauthenticated network access required.
  • Exploitable via unsupported HTTP methods.
  • Leads to unauthorized access.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, a remote unauthenticated attacker could bypass authentication for EJB JAX-WS endpoints by using HTTP methods not protected by the configured security constraints, potentially affecting service integrity and confidentiality.

  • EJB JAX-WS endpoint configurations.
  • Unprotected HTTP methods bypass authentication.
  • Service integrity and confidentiality may be affected.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in EJB JAX-WS endpoints requires immediate attention from teams responsible for application development and infrastructure. The first practical step is to identify all instances of the affected technology, determine their exposure and criticality, and then assign ownership for remediation. This will likely involve collaboration between application owners, platform teams, and potentially network and security teams to prioritize and plan the necessary upgrades or mitigation strategies.

  • Application and platform teams own the issue.
  • Confirm EJB JAX-WS endpoint exposure and criticality.
  • Plan and coordinate necessary 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 EJB JAX-WS, and why is it used?

EJB JAX-WS (Enterprise JavaBeans Java API for XML Web Services) is a technology framework used to build and manage web services in Java applications. It allows different systems to communicate by exchanging structured data, often serving as the backbone for APIs that connect distributed software components or allow external clients to interact with backend business logic.

How does this CVE-2026-111264 authentication bypass work?

This vulnerability involves a weakness categorized as CWE-288, which refers to authentication bypass via an alternate path. In this specific case, the software incorrectly applies security restrictions only to certain common HTTP methods. Because the security filter is incomplete, an attacker can use a different, less-common HTTP method to reach the endpoint, effectively skipping the authentication check entirely.

Do I need to worry about all requests to these endpoints?

No, not all requests will trigger this vulnerability. The bypass occurs specifically when a request is made using an HTTP method that was not explicitly included in the developer's security configuration. Standard requests that happen to use the protected methods are still subject to normal authentication controls.

How do I know if my systems are relevant?

Halo Surface Signal indicates that EJB JAX-WS endpoints are commonly deployed as web services or APIs. If your organization uses these endpoints to facilitate communication across your network or exposes them as public-facing APIs, your systems are likely reachable from the internet. This connectivity makes them a relevant part of your external attack surface.

When should I prioritize fixing this vulnerability?

You should prioritize this immediately by first conducting an inventory to locate all instances of EJB JAX-WS endpoints within your environment. Once identified, assess the criticality of each service and coordinate with your application development and platform teams to schedule the necessary software upgrades to the versions specified in the advisory.

References