Skip to main content
CVE-2026-111241VulnerabilityPublished

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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-111241· High

Not known to be exploited · fixed in 11.0.0-M2 : patch Apache TomEE soon.

Data as of 10 Nov 2026, 19:05 UTC

Severity
High

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 11.0.0-M2, 10.3.0, 10.0.0-M1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Upgrade Apache TomEE and org.apache.tomee/openejb-core to 11.0.0-M2, 10.3.0 or 10.0.0-M1.

Affected software

ProductAffectedFixed in
Apache TomEEorg.apache.openejb:openejb-coreAffected
  • >=4.0.0-beta-1 <=4.7.5
Fixed in–
Apache TomEEorg.apache.tomee:openejb-coreAffected
  • >=11.0.0-M1 <11.0.0-M2
Fixed in
  • 11.0.0-M2
Apache TomEEorg.apache.tomee:openejb-coreAffected
  • >=10.0.0-M1 <10.3.0
Fixed in
  • 10.3.0
Apache TomEEorg.apache.tomee:openejb-coreAffected
  • >=7.0.0-M1 <10.0.0-M1
Fixed in
  • 10.0.0-M1
Mavenorg.apache.openejb/openejb-corepkg:maven/org.apache.openejb/openejb-coreOther threatsAffected
  • >=4.0.0-beta-1 <=4.7.5
Fixed in–
Mavenorg.apache.tomee/openejb-corepkg:maven/org.apache.tomee/openejb-coreOther threatsAffected
  • >=7.0.0-M1 <10.0.0-M1
  • >=10.0.0-M1 <10.3.0
  • >=11.0.0-M1 <11.0.0-M2
Fixed in
  • 10.0.0-M1
  • 10.3.0
  • 11.0.0-M2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

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.

References

Community reviews

Loading reviews…