CVE-2026-111263 json
Apache TomEE: Missing authentication on EJB web service endpoints deployed in a web application
published yesterday modified yesterday also EUVD-2026-121218
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
Authentication configured for an EJB JAX-WS endpoint in the TomEE deployment descriptor is not enforced when the endpoint is published within an existing web application. A remote unauthenticated attacker can invoke the web service operations, unless the application protects the endpoint with its own web.xml security constraints or EJB method permissions. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.
Patch / fix
- maven org.apache.tomee:tomee-webservices 10.0.0-M1, 10.3.0, 11.0.0-M2
- Apache Software Foundation Apache TomEE 10.0.0-M1, 10.3.0, 11.0.0-M2
Is CVE-2026-111263 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.openejb:tomee-webservices | >=4.0.0-beta-1, <=4.0.0 >=1.5.0, <=1.7.5 |
no fix listed |
| maven | org.apache.tomee:tomee-webservices | >=7.0.0-M1, <10.0.0-M1 >=10.0.0-M1, <10.3.0 >=11.0.0-M1, <11.0.0-M2 |
10.0.0-M1 10.3.0 11.0.0-M2 |
Affected products
- Apache Software Foundation Apache TomEE
Classification
- Weakness
-
- CWE-306 Missing Authentication for Critical Functionality
References
-
lists.apache.org
/thread.html/bgk825mdkyxfrlnbfszmlmbwmlk1qlhl
vendor-advisory
Sources
- CVE List CVE-2026-111263
- NVD CVE-2026-111263
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.