CVE-2026-87755
Apache TomEE: Stateful session bean hijacking via predictable session identifiers
Stateful session bean identifiers are not generated from a cryptographically secure random source. A remote attacker with access to the EJB remote endpoint who holds one valid identifier can derive those of other clients' sessions and invoke methods on their beans, exposing or modifying other users' session state. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Apache TomEE Apache Software Foundation org.apache.openejb:openejb-core
maven |
≥ 4.0.0-beta-1; ≤ 4.7.5 (affected, semver)
Other versions: unaffected |
CNA: apache |
| Apache TomEE Apache Software Foundation org.apache.tomee:openejb-core
maven |
≥ 7.0.0-M1; < 10.0.0-M1 (affected, semver) ≥ 10.0.0-M1; < 10.3.0 (affected, semver) ≥ 11.0.0-M1; < 11.0.0-M2 (affected, semver) Other versions: unaffected |
CNA: apache |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://lists.apache.org/thread.html/srzp26oyjtb3bwgxwsyhpphv778s17m8CNA: apache · vendor-advisory
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.