CVE-2026-111241 · Runtime
NO FIX YET · SEE WHAT TO DO
When a non-default stateful session bean passivation strategy is enabled, passivated bean state is saved to predictably named files in the shared system temporary directory and reused if they already exist. The server deserializes that data on activation, so a local user who can write to that directory can read session state or supply data that may lead to code execution as the server process.
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.
Only servers where a non-default stateful session bean passivation strategy is configured are exposed, since passivation is what writes state to the temp directory. The risk requires a local attacker who can write to the shared system temporary directory on that machine. Servers using default configuration can skip it.
Not affected if default-config, no-local-untrusted-users
Who cares application-server, java, self-hosted
10.3.0 or 11.0.0-M2.10.3.0 or 11.0.0-M2, per the sources.When a non-default stateful session bean passivation strategy is configured, passivated bean state is written to predictably named files in the shared system temporary directory, reusing files that already exist there, and is deserialized on activation. A local attacker who can write to that directory can read passivated session state or supply data that the server deserializes, potentially leading to code execution as the server process. 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.