VulnerabilityPublished 10 Nov 2026

CVE-2026-111247: Apache TomEE · Incorrect Authorization

Affects Apache TomEESource CVE Database V5

Compare

Not known to be exploited · fixed in 11.0.0-M2 : patch Apache TomEE soon.

Data as of 10 Nov 2026, 15:35 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in 11.0.0-M2, 10.3.0, 10.0.0-M1

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Apache TomEE and org.apache.tomee/tomee-catalina to 11.0.0-M2, 10.3.0 or 10.0.0-M1.

Affected software

Product	Affected	Fixed in
Apache TomEEorg.apache.tomee:tomee-catalina	Affected >=11.0.0-M1 <11.0.0-M2	Fixed in 11.0.0-M2
Apache TomEEorg.apache.tomee:tomee-catalina	Affected >=10.0.0-M1 <10.3.0	Fixed in 10.3.0
Apache TomEEorg.apache.tomee:tomee-catalina	Affected >=8.0.7 <10.0.0-M1	Fixed in 10.0.0-M1
Mavenorg.apache.tomee/tomee-catalina`pkg:maven/org.apache.tomee/tomee-catalina`Other threats	Affected >=8.0.7 <10.0.0-M1 >=10.0.0-M1 <10.3.0 >=11.0.0-M1 <11.0.0-M2	Fixed in 10.0.0-M1 10.3.0 11.0.0-M2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Apache TomEE to version 10.3.0 or 11.0.0-M2 or later, where this incorrect authorization issue is fixed. No other mitigation or temporary workaround is indicated.

Description

CVE-2026-111247 is an incorrect authorization vulnerability in Apache TomEE where a user's name is incorrectly treated as a role name during authorization checks. An attacker who can register an account with a username matching a role name can gain unauthorized access to that role's permissions. The issue is fixed in Apache TomEE versions 10.3.0 and 11.0.0-M2.

Impact

An authenticated attacker who can register or obtain an account with a username matching a role name can escalate privileges by being granted that role's permissions improperly. This leads to unauthorized access and potential privilege escalation within applications using Apache TomEE's Jakarta Authorization policy.

Summary

This vulnerability arises because when resolving security roles for a realm-authenticated caller, the caller's username is also considered a role name in addition to the roles assigned by the realm. This allows an authenticated attacker who can create or obtain an account with a username identical to a role name to be granted that role's permissions wherever Jakarta Authorization policy is used for authorization. The flaw affects Apache TomEE versions from 8.0.7 up to but not including 10.0.0-M1, from 10.0.0-M1 up to but not including 10.3.0, and from 11.0.0-M1 up to but not including 11.0.0-M2. The issue is resolved in versions 10.3.0 and 11.0.0-M2.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

lists.apache.org/thread/wmx75ytmp7d5h8cnd8jf1lg2gbw983f3 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Nov 2026, 15:35 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats