CVE-2026-97872
apache software foundation apache tomee: no CVSS score yet.
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.
- CWE
- CWE-306 Missing Authentication for Critical Functionality
- OWASP Top 10
- A07:2025 Authentication Failures
- Published
- Assigned by
- apache (CNA)
- NVD analysis
- Not in the NVD yet
- Record from
- the CVE List, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-97872 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97872?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97872?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-97872 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
- apache software foundation:apache tomee
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Apache Software Foundation Apache TomEE | from 4.6.0 through 4.7.5 |
| Apache Software Foundation Apache TomEE | from 7.0.0-M1 before 10.0.0-M1 |
| Apache Software Foundation Apache TomEE | from 10.0.0-M1 through 10.2.0 |
| Apache Software Foundation Apache TomEE | 11.0.0-M1 |
Attack patterns (CAPEC)
- CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
- CAPEC-36 Using Unpublished Interfaces or Functionality Likelihood: Medium · Severity: High
- CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
- CAPEC-166 Force the System to Reset Values Severity: Medium
- CAPEC-216 Communication Channel Manipulation
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.