CVE-2026-97867: The EJBd remote protocol returns datasource connection details, including database credentials, to
Source GCVE Database
Not known to be exploited · fixed in 11.0.0-M2 : patch Apache TomEE soon.
Data as of 10 Nov 2026, 19:05 UTC
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
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-ejbd to 11.0.0-M2, 10.3.0 or 10.0.0-M1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache TomEEorg.apache.openejb:openejb-ejbd | Affected
| Fixed in– |
| Apache TomEEorg.apache.tomee:openejb-ejbd | Affected
| Fixed in
|
| Apache TomEEorg.apache.tomee:openejb-ejbd | Affected
| Fixed in
|
| Apache TomEEorg.apache.tomee:openejb-ejbd | Affected
| Fixed in
|
Mavenorg.apache.openejb/openejb-ejbdpkg:maven/org.apache.openejb/openejb-ejbdOther threats | Affected
| Fixed in– |
Mavenorg.apache.tomee/openejb-ejbdpkg:maven/org.apache.tomee/openejb-ejbdOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The EJBd remote protocol returns datasource connection details, including database credentials, to remote clients that look up a datasource. A remote client able to reach the EJBd endpoint can obtain the database credentials and connect to the database directly. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.