Skip to content
Fencer Intel
medium —

CVE-2026-111239 json

Apache TomEE: Code execution by any authenticated user via the SSH administration shell

published yesterday modified 23h ago also EUVD-2026-121256

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

Summary

The optional SSH administration service grants full access to the administration shell to every user that authenticates against its configured login domain, without checking for an administrative role. An attacker holding the credentials of any user in that domain, including a low-privileged application user, can execute arbitrary code as the server process. Users are recommended to disable the SSH administration service, or to block network access to it from untrusted clients and restrict its login domain to administrative users.

Patch / fix

  • maven org.apache.tomee:openejb-ssh 10.0.0-M1
  • maven org.apache.tomee:openejb-common-cli 10.0.0-M1
  • Apache Software Foundation Apache TomEE 10.0.0-M1

Is CVE-2026-111239 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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
yesterday

Exploit prediction

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

Affected packages

ecosystem package affected fixed in
maven org.apache.openejb:openejb-ssh
>=4.0.0, <=4.7.5
no fix listed
maven org.apache.tomee:openejb-ssh
>=7.0.0-M1, <10.0.0-M1
>=10.0.0-M1, <=10.2.0
11.0.0-M1
10.0.0-M1
maven org.apache.openejb:openejb-common-cli
>=4.0.0, <=4.7.5
no fix listed
maven org.apache.tomee:openejb-common-cli
>=7.0.0-M1, <10.0.0-M1
>=10.0.0-M1, <=10.2.0
11.0.0-M1
10.0.0-M1

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.