CVE-2026-111256: Apache TomEE: embedded OpenEJB skips JAX-WS/RS auth

AWAITING NVD

Published November 10, 2026

CISO Take

Apache TomEE's embedded OpenEJB HTTP server silently ignores some configured authentication methods on JAX-WS and JAX-RS endpoints, so those endpoints are published with no authentication at all (CWE-306). A remote unauthenticated attacker can call the exposed operations directly, with no credentials and no user interaction. No CVSS, EPSS, KEV or public exploit data exists yet, so the severity is unscored, and exposure is limited to deployments that use the embedded HTTP server rather than the Tomcat-based TomEE distributions. This is a Java enterprise middleware flaw and it is not an AI-native vulnerability. It matters only where ML or LLM services are exposed as SOAP or REST endpoints on the embedded server and rely on the ignored authentication. Inventory any TomEE or OpenEJB embedded deployments, block untrusted network access to the embedded HTTP port, and migrate to the Tomcat-based TomEE distributions, following the Apache advisory.

Sources:NVDATLASapache.org

What is the risk?

Risk is unscored for now because CVSS, EPSS and SSVC data are not yet available. The flaw is a missing-authentication condition (CWE-306) that is network-reachable without credentials, which would usually put it in the high-to-critical range for affected deployments. Exposure is narrow: only the embedded OpenEJB HTTP server is affected, and only when a configured authentication method is silently dropped. There is no known public exploit, Nuclei template or KEV listing as of publication. The AI/ML relevance is indirect and the package-level risk score is 0/100. Reassess when NVD or CISA scoring appears.

How does the attack unfold?

Discovery

The attacker locates an embedded OpenEJB HTTP server exposing JAX-WS or JAX-RS endpoints.

AML.T0006

Initial Access

The attacker sends unauthenticated requests that the server accepts because the configured authentication method is silently ignored.

AML.T0049

Impact

The attacker invokes exposed operations to read data, call backend AI services or trigger actions without authorization.

AML.T0040

Discovery

The attacker locates an embedded OpenEJB HTTP server exposing JAX-WS or JAX-RS endpoints.

AML.T0006

Initial Access

The attacker sends unauthenticated requests that the server accepts because the configured authentication method is silently ignored.

AML.T0049

Impact

The attacker invokes exposed operations to read data, call backend AI services or trigger actions without authorization.

AML.T0040

How severe is it?

CVSS 3.1

N/A

EPSS

0.2%

chance of exploitation in 30 days

Higher than 12% of all CVEs

Source: EPSS v3 — FIRST.org

Exploitation Status

No known exploitation

Sophistication

Trivial

What should I do?

1 step

1) Inventory applications that embed OpenEJB's HTTP server, for example through embedded containers, test harnesses or the EJBd/HTTP services. 2) Block network access to the embedded HTTP server from untrusted clients with firewall rules, network segmentation or a reverse proxy that enforces authentication. 3) Migrate to the Tomcat-based TomEE distributions, where authentication is enforced. 4) Apply any fixed release Apache announces on the project mailing list thread (lists.apache.org/thread/pfspkd8c0d5pxx3k04vnfvrn979tz1zo). 5) For detection, probe your own JAX-WS and JAX-RS endpoints without credentials to confirm that authentication is enforced, and review access logs for unauthenticated calls to protected operations.

How is it classified?

Auth BypassAPIFrameworkAML.T0040- AI Model Inference API Access AML.T0049- Exploit Public-Facing Application

Which compliance frameworks are affected?

This CVE is relevant to:

ISO 42001

A.6.2.6-AI system operation and monitoring

NIST AI RMF

MANAGE 2.3-Responses to previously unknown risks and mechanisms to supersede or deactivate AI systems

OWASP LLM Top 10

LLM03-Supply Chain

Frequently Asked Questions

What is CVE-2026-111256?

Is CVE-2026-111256 actively exploited?

No confirmed active exploitation of CVE-2026-111256 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-111256?

1) Inventory applications that embed OpenEJB's HTTP server, for example through embedded containers, test harnesses or the EJBd/HTTP services. 2) Block network access to the embedded HTTP server from untrusted clients with firewall rules, network segmentation or a reverse proxy that enforces authentication. 3) Migrate to the Tomcat-based TomEE distributions, where authentication is enforced. 4) Apply any fixed release Apache announces on the project mailing list thread (lists.apache.org/thread/pfspkd8c0d5pxx3k04vnfvrn979tz1zo). 5) For detection, probe your own JAX-WS and JAX-RS endpoints without credentials to confirm that authentication is enforced, and review access logs for unauthenticated calls to protected operations.

What systems are affected by CVE-2026-111256?

This vulnerability affects the following AI/ML architecture patterns: model serving, inference APIs, Java enterprise service gateways, data pipelines.

What is the CVSS score for CVE-2026-111256?

No CVSS score has been assigned yet.

What is the AI security impact?

Affected AI Architectures

model servinginference APIsJava enterprise service gatewaysdata pipelines

MITRE ATLAS Techniques

AML.T0040AI Model Inference API Access

AML.T0049Exploit Public-Facing Application

Compliance Controls Affected

ISO 42001: A.6.2.6

NIST AI RMF: MANAGE 2.3

OWASP LLM Top 10: LLM03

What are the technical details?

Original Advisory

When JAX-WS or JAX-RS endpoints are published by the embedded OpenEJB HTTP server rather than Tomcat, some configured authentication methods are silently ignored and the endpoint is published without authentication. A remote unauthenticated attacker can invoke the exposed operations without credentials. Only deployments that use the embedded HTTP server and rely on such an authentication method are affected. Users are recommended to block network access to the embedded HTTP server from untrusted clients, or to migrate to the Tomcat based TomEE distributions.

Exploitation Scenario

An attacker scans for an internet-exposed or internally reachable embedded OpenEJB HTTP listener that hosts a JAX-RS or JAX-WS service, for example an ML inference or data-enrichment API that the team believed was protected by basic or token authentication. The attacker sends requests without credentials, and the server accepts them because the authentication method was silently ignored. They invoke the exposed operations to read model outputs or training and feature data, submit arbitrary inference requests that consume resources, or trigger administrative functions in the service.

Weaknesses (CWE)

CWE-306Missing Authentication for Critical FunctionalityPrimary CWE-306Missing Authentication for Critical Functionality

CWE-306 — Missing Authentication for Critical Functionality: The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

[Architecture and Design] Divide the software into anonymous, normal, privileged, and administrative areas. Identify which of these areas require a proven user identity, and use a centralized authentication capability. Identify all potential communication channels, or other means of interaction with the software, to ensure that all channels are appropriately protected, including those channels that are assumed to be accessible only by authorized parties. Developers sometimes perform authentication at the primary channel, but open up a secondary channel that is assumed to be private. For example, a login mechanism may be listening on one network port, but after successful authentication, it may open up a second port where it waits for the connection, but avoids authentication because it assumes that only the authenticated party will connect to the port. In general, if the software or protocol allows a single session or user state to persist across multiple connections or channels, authentication and appropriate
[Architecture and Design] For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.

Source: MITRE CWE corpus.