CVE-2026-111256 · Runtime
NO FIX YET · SEE WHAT TO DO
When JAX-WS or JAX-RS web endpoints are published by the embedded OpenEJB HTTP server instead of Tomcat, some configured authentication methods are silently ignored. An remote attacker with no credentials can call the exposed operations.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Only deployments that publish JAX-WS or JAX-RS endpoints through the embedded OpenEJB HTTP server and rely on an authentication method that the server ignores are exposed. Applications served by Tomcat-based TomEE are not described as affected.
Not affected if no-auth-dependency, no-jax-ws-or-jax-rs, tomcat-based-tomee
Who cares java, jax-rs, jax-ws, openejb, tomee
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.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.