Quick answers
- Is CVE-2026-111241 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111241 being exploited in the wild.
- How severe is CVE-2026-111241?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Oracle GlassFish before 10.3.0 and 11.0.0-M2.
- Is there a fix for CVE-2026-111241?
- Yes: fixed in GlassFish 10.3.0, 11.0.0-M2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111241 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-111241?
- Check whether you run Oracle GlassFish at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: GlassFish 10.3.0, 11.0.0-M2
Technical details
The vulnerability occurs in stateful session bean passivation when a non-default passivation strategy is configured: serialized bean state is written to the shared system temporary directory in predictable file locations, and those files are reused rather than uniquely named. An unauthenticated local attacker who can write to the system temp directory can either read passivated session state or replace it with malicious serialized data, leading to deserialization code execution when the bean is activated. The vulnerability requires local file system access but no prior authentication or network connectivity.
Affected products
- Oracle GlassFish before 10.3.0 and 11.0.0-M2
Timeline
- 2026-11-10: disclosed