- Exploited
- No known exploitation
- Fix
- Fixed in 10.0.0-M1, 10.3.0, 11.0.0-M2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 10.0.0-M1, 10.3.0, 11.0.0-M2.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Apache TomEE contains a privilege escalation flaw in which a logged-in user whose user name matches a role name is granted that role when authorization is checked through the Jakarta Authorization policy. An attacker who can create or obtain such an account, for example through self-registration, could gain the privileges of that role; the flaw is reached only after the attacker has authenticated.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach10/20Affects Maven packages
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 10.0.0-M1, 10.3.0, 11.0.0-M2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-111247 (Apache TomEE: Privilege escalation via user name matching a role name), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-111247 (entry last updated 2026-11-10): Affected: - Maven package org.apache.tomee:tomee-catalina: from 8.0.7, fixed in 10.0.0-M1; from 10.0.0-M1, fixed in 10.3.0; from 11.0.0-M1, fixed in 11.0.0-M2 Fixed versions: 10.0.0-M1, 10.3.0, 11.0.0-M2. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-111247 is not listed as of cve.now's last read. This KEV status is for CVE-2026-111247 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Packages (Maven): find every lockfile in each project and run check_stack from the cve.now MCP server on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies. Verify against the linked advisories before concluding, and cite the date you read each one: - https://lists.apache.org/thread/wmx75ytmp7d5h8cnd8jf1lg2gbw983f3 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-111247 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-111247.
Timeline
- CVE published
- First seen by cve.now
Affected versions
From 8.0.7 · fixed in 10.0.0-M1; From 10.0.0-M1 · fixed in 10.3.0; From 11.0.0-M1 · fixed in 11.0.0-M2
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-111247
Is CVE-2026-111247 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-111247?
org.apache.tomee:tomee-catalina (Maven): from 8.0.7 before 10.0.0-M1; from 10.0.0-M1 before 10.3.0; from 11.0.0-M1 before 11.0.0-M2.Source: cve.now feed data
How do I fix CVE-2026-111247?
Upgrade to a fixed version: 10.0.0-M1, 10.3.0, 11.0.0-M2.Source: cve.now feed data