OPENEJB · CVE-2026-111245 · Runtime
NO FIX YET · SEE WHAT TO DO
After a successful WS-Security UsernameToken login, OpenEJB's standalone HTTP server keeps the caller's identity attached to the worker thread after the request ends. A later unauthenticated request handled on that same thread can call protected EJB methods as the previously logged-in user.
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.
Systems running the standalone OpenEJB HTTP server that expose web services secured with WS-Security UsernameToken authentication. Applications that use OpenEJB only inside a different container, or that do not serve web services over that HTTP server, are not described as affected by the sources.
Not affected if no-web-services, other-container
Who cares java, openejb, web-services, ws-security
openejb-core in pom.xml or build.gradle).10.3.011.0.0-M2After a successful WS-Security UsernameToken authentication, the caller identity stays associated with the worker thread once the request completes when web services are served by the standalone OpenEJB HTTP server. A remote unauthenticated attacker whose request is later processed on the same thread can invoke protected EJB methods with the identity of a previously authenticated user. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.
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.