Skip to content
Fencer Intel
medium —

CVE-2026-111256 json

Apache TomEE: Missing authentication for web service endpoints in embedded HTTP server

published yesterday modified yesterday also EUVD-2026-121225

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

When JAX-WS or JAX-RS endpoints are published by the embedded OpenEJB HTTP server rather than Tomcat, some configured authentication methods are silently ignored and the endpoint is published without authentication. A remote unauthenticated attacker can invoke the exposed operations without credentials. Only deployments that use the embedded HTTP server and rely on such an authentication method are affected. Users are recommended to block network access to the embedded HTTP server from untrusted clients, or to migrate to the Tomcat based TomEE distributions.

Patch / fix

  • maven org.apache.tomee:openejb-webservices 10.0.0-M1
  • maven org.apache.tomee:openejb-rest 10.0.0-M1
  • Apache Software Foundation Apache TomEE 10.0.0-M1

Is CVE-2026-111256 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:openejb-webservices
>=4.0.0-beta-1, <=4.7.5
 no fix listed
maven org.apache.openejb:openejb-rest
>=4.6.0, <=4.7.5
 no fix listed
maven org.apache.tomee:openejb-webservices
>=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.tomee:openejb-rest
>=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
  • CWE-306 Missing Authentication for Critical Functionality

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.