CVE-2026-97872 · Runtime
NO FIX YET
When an EJB is exposed over the optional Hessian protocol inside a web application, some configured authentication and transport security settings are silently not enforced. A remote unauthenticated attacker can invoke the exposed EJB methods.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Only deployments that expose an EJB through the Hessian module with the affected authentication and transport security settings. Systems that do not use Hessian remoting are not described as affected. Teams that run such endpoints should block network access to Hessian endpoints from untrusted clients or migrate to another remoting protocol, as the description recommends.
Not affected if no-hessian-endpoints, other-remoting-protocol
Who cares ejb, hessian, java, self-hosted
Unknown from the sources.
Unknown from the sources.
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.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.