Description
This is a concurrency issue that can result in the wrong caller principal being returned from the session context of an EJB that is configured with a RunAs principal. In particular, the org.jboss.as.ejb3.component.EJBComponent class has an incomingRunAsIdentity field. This field is used by the org.jboss.as.ejb3.security.RunAsPrincipalInterceptor to keep track of the current identity prior to switching to a new identity created using the RunAs principal. The exploit consist that the EJBComponent#incomingRunAsIdentity field is currently just a SecurityIdentity. This means in a concurrent environment, where multiple users are repeatedly invoking an EJB that is configured with a RunAs principal, it's possible for the wrong the caller principal to be returned from EJBComponent#getCallerPrincipal. Similarly, it's also possible for EJBComponent#isCallerInRole to return the wrong value. Both of these methods rely on incomingRunAsIdentity. Affects all versions of JBoss EAP from 7.1.0 and all versions of WildFly 11+ when Elytron is enabled.
Remediation
References
Related Vulnerabilities
Next.js Server-Side Request Forgery (SSRF) Vulnerability (CVE-2026-64649)
MediaWiki Improper Control of Generation of Code ('Code Injection') Vulnerability (CVE-2026-58025)
MySQL CVE-2013-1502 Vulnerability (CVE-2013-1502)
ASP.NET MVC Improper Authentication Vulnerability (CVE-2018-8171)
Jetty Improper Input Validation Vulnerability (CVE-2025-11143)