CVE-2026-111247 · Runtime
NO FIX YET · SEE WHAT TO DO
When a realm-authenticated user is checked for roles, the user's own name is also counted as a role name alongside the realm's roles. An attacker who gets an account whose name matches a role name is granted that role wherever Jakarta Authorization policy is evaluated.
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.
Applications that authenticate users through a realm and rely on Jakarta Authorization role checks are exposed. The risk needs an account whose user name equals a role name, which self-registration can allow. The sources do not say which product or configuration this applies to, so the affected software must be identified first.
Not affected if no-role-named-users, no-self-registration
Who cares jakarta-authorization, realm-authentication
Unknown from the sources.
10.3.0 or 11.0.0-M2, the versions the source names as fixed; the sources do not name the product.When resolving security roles of a realm-authenticated caller, the caller's user name is also treated as a role name in addition to the roles assigned by the realm. An authenticated attacker who can obtain an account whose user name equals a role name, for example through self-registration, is granted that role wherever authorization is evaluated through the Jakarta Authorization policy. 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.