Skip to content
Fencer Intel
medium —

CVE-2026-111258 json

Apache TomEE: Security constraint bypass via request routing

published yesterday modified yesterday also EUVD-2026-121223

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 11%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.apache.tomee:tomee-catalina 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-111258 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 Fencer

Exploit prediction

0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-11).

Affected packages

ecosystem package affected fixed in
maven org.apache.openejb:tomee-catalina
>=1.5.0, <=1.7.5
 no fix listed
maven org.apache.tomee:tomee-catalina
>=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

References

Sources

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.