Apache TomEE: Stateful session bean hijacking via predictable session identifiers
Severity and exploitation
KEV coverage does not rule out exploitation.
Severity
unknownCVSS 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.0.0-beta-1 to 4.7.5, 7.0.0-M1 to 10.0.0-M1, and 11.0.0-M1 to 11.0.0-M2 have a weakness where stateful session bean identifiers are predictable, allowing a remote attacker with access to the EJB remote endpoint to invoke methods on other clients' sessions. The attacker must hold one valid identifier. The impact is exposure or modification of other users' session state.
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 Software Foundation · apache
Apache TomEE
Package identity
pkg:maven/org.apache.openejb/openejb-coreExplore org.apache.openejb:openejb-core →Identity supplied by apache. Version matching requires compatible range evidence.
Compare with this publisher’s ranges. This does not inspect your installation.
affected
4.0.0-beta-1 → through 4.7.5
semver versions
Other versions: unaffected
Apache Software Foundation · apache
Apache TomEE
3 ranges
Apache Software Foundation · apache
Apache TomEE
Package identity
pkg:maven/org.apache.tomee/openejb-coreExplore org.apache.tomee:openejb-core →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 → before 10.3.0
semver versions
11.0.0-M1 → before 11.0.0-M2
semver versions
Other versions: unaffected
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
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.
References
1 sourcesInside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-87755View 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.
Contributing organizations · 1
Assigning organization
Timeline
All times UTCAdvisory published
Publication date supplied by the source.
Last imported by cve.new
Latest catalog import, not the date we first saw this advisory.
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.