CVE-2026-86811 · Runtime
NO FIX YET · SEE WHAT TO DO
A stateful session bean's passivation mechanism builds its on-disk file name from a client-supplied identifier without checking it. A remote attacker with access to the remote EJB service can read or write session state in files outside the passivation directory.
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.
Systems that run a Java application server with stateful session beans passivated to disk and a remote EJB service reachable by clients. Servers without remote EJB access, or without stateful session beans, are not described as exposed. The sources do not name the affected product, so confirm the server product before acting on the version list.
Not affected if no-remote-ejb-service
Who cares ejb, java, stateful-session-beans
10.3.0 (10.x line) and 11.0.0-M2 (11.x line); older versions are the ones named in the advisory.10.3.0 on the 10.x line.11.0.0-M2 on the 11.x line.The stateful session bean passivation mechanism derives the on-disk file name from a client-supplied identifier without validating it. A remote attacker with access to the remote EJB service can cause session state to be read from or written to files outside the passivation directory. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.
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.