Skip to content
Fencer Intel
medium —

CVE-2026-97872 json

Apache TomEE: Authentication bypass of Hessian EJB endpoints due to ignored security settings

published yesterday modified yesterday also EUVD-2026-121157

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 an EJB is exposed over the optional Hessian protocol inside an existing web application, some configured authentication and transport security settings are silently not enforced. A remote unauthenticated attacker can invoke the exposed EJB methods. Only deployments using the Hessian module with such settings are affected. Users are recommended to block network access to Hessian endpoints from untrusted clients, or to migrate to another remoting protocol.

Patch / fix

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

Is CVE-2026-97872 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-hessian
>=4.6.0, <=4.7.5
 no fix listed
maven org.apache.tomee:openejb-hessian
>=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.