Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.newCreate a CVE report
Check your stack
CVE-2026-97872

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

Products / packages Apache Software Foundation Apache TomEE

Published

Share

Severity and exploitation

Not in CISA KEVNo CVSS score

KEV coverage does not rule out exploitation.

KEV checked 14/11/2026, 21:30:34 UTC

Severity

unknown

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Fix status not established

No structured fix or guidance is available here. Check the latest publisher advisory.

What this means

Apache TomEE versions 4.6.0 to 4.7.5, 7.0.0-M1 to 10.2.0, and 11.0.0-M1 have an authentication bypass weakness in Hessian EJB endpoints, allowing remote unauthenticated attackers to invoke exposed EJB methods. The issue occurs when the Hessian module is used with ignored security settings. Affected deployments can block network access to Hessian endpoints or migrate to another remoting protocol.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

Apache Software Foundation · apache

Apache TomEE

1 range
apache version evidence

Package identity

pkg:maven/org.apache.openejb/openejb-hessianExplore org.apache.openejb:openejb-hessian →

Identity supplied by apache. Version matching requires compatible range evidence.

Compare with this publisher’s ranges. This does not inspect your installation.

affected

4.6.0 → through 4.7.5

semver versions

unaffected

unknown

Other versions: unaffected

Apache Software Foundation · apache

Apache TomEE

3 ranges
apache version evidence

Package identity

pkg:maven/org.apache.tomee/openejb-hessianExplore org.apache.tomee:openejb-hessian →

Identity supplied by apache. Version matching requires compatible range evidence.

Compare with this publisher’s ranges. This does not inspect your installation.

affected

7.0.0-M1 → before 10.0.0-M1

semver versions

10.0.0-M1 → through 10.2.0

semver versions

11.0.0-M1

semver versions

unaffected

unknown

Other versions: unaffected

Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

No structured fix or remediation guidance is available here. Check the full source description and vendor’s latest advisory for a patch or workaround; do not assume another version is safe.

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher description

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.

References

1 sources
lists.apache.org/thread/hythwhxfnmghgv21y2pw73s41qt99z72
Vendor advisoryapache

Inside the record

Evidence available

Package identity
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-97872

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-306 ↗

CWE-306 Missing Authentication for Critical Function

apache

Related →
Contributing organizations · 1
apache

Assigning organization

2026-11-10

Timeline

All times UTC

  1. Advisory published

    Publication date supplied by the source.

  2. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.