Skip to main content
CVE-2026-111245VulnerabilityPublished

After a successful WS-Security UsernameToken authentication, the caller identity stays associated with the worker thread once the request completes when web services are served by the standalone OpenEJB HTTP server

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-111245· 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-cxf to 11.0.0-M2, 10.3.0 or 10.0.0-M1.

Affected software

ProductAffectedFixed in
Apache TomEEorg.apache.openejb:openejb-cxfAffected
  • >=4.0.0-beta-1 <=4.7.5
Fixed in–
Apache TomEEorg.apache.tomee:openejb-cxfAffected
  • >=11.0.0-M1 <11.0.0-M2
Fixed in
  • 11.0.0-M2
Apache TomEEorg.apache.tomee:openejb-cxfAffected
  • >=10.0.0-M1 <10.3.0
Fixed in
  • 10.3.0
Apache TomEEorg.apache.tomee:openejb-cxfAffected
  • >=7.0.0-M1 <10.0.0-M1
Fixed in
  • 10.0.0-M1
Mavenorg.apache.openejb/openejb-cxfpkg:maven/org.apache.openejb/openejb-cxfOther threatsAffected
  • >=4.0.0-beta-1 <=4.7.5
Fixed in–
Mavenorg.apache.tomee/openejb-cxfpkg:maven/org.apache.tomee/openejb-cxfOther 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

After a successful WS-Security UsernameToken authentication, the caller identity stays associated with the worker thread once the request completes when web services are served by the standalone OpenEJB HTTP server. A remote unauthenticated attacker whose request is later processed on the same thread can invoke protected EJB methods with the identity of a previously authenticated user. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.

References

Community reviews

Loading reviews…