CVE-2026-111258: high-severity vulnerability in Apache TomEE
Apache TomEE: Security constraint bypass via request routing
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 0.5%
The optional request routing feature forwards requests to their configured destination without applying the security constraints of that destination or the protection of the web application's private directories. If a route copies client-controlled parts of the request path into its destination, a remote attacker can reach protected resources or read application configuration and class files. Only installations with such a routing configuration are affected. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Affected products
Apache Software Foundation · Apache TomEERelated CVEs — Apache TomEE
In the same product, most dangerous first.
CVE-2018-8031—CVE-2018-8031EPSS 2.0%CVE-2026-87756CRITICALApache TomEE: Missing authorization on internal deployer EJBs in default profileEPSS 0.7%CVE-2026-111264CRITICALApache TomEE: Authentication bypass on EJB web service endpoints via HTTP methodEPSS 0.7%CVE-2026-111244CRITICALApache TomEE: Authorization bypass in MicroProfile JWT role checks for JAX-RS resourcesEPSS 0.6%CVE-2026-97881HIGHApache TomEE: Path traversal in embedded HTTP server static resource handlingEPSS 0.6%CVE-2026-86811HIGHApache TomEE: Path traversal via stateful EJB passivationEPSS 0.6%