VulnerabilityPublished 10 Nov 2026

CVE-2026-111262: Apache TomEE · LDAP Injection

Affects Apache TomEESource CVE Database V5

Compare

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

Data as of 10 Nov 2026, 15:21 UTC

Severity

High

Rated High by Threat Radar's AI analysis · 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

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

Affected software

Product	Affected	Fixed in
Apache TomEEorg.apache.tomee:tomee-security	Affected >=11.0.0-M1 <11.0.0-M2	Fixed in 11.0.0-M2
Apache TomEEorg.apache.tomee:tomee-security	Affected >=10.0.0-M1 <10.3.0	Fixed in 10.3.0
Apache TomEEorg.apache.tomee:tomee-security	Affected >=8.0.4 <10.0.0-M1	Fixed in 10.0.0-M1
Mavenorg.apache.tomee/tomee-security`pkg:maven/org.apache.tomee/tomee-security`Other threats	Affected >=8.0.4 <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.

AI-suggested

Users should upgrade affected Apache TomEE installations to version 10.3.0 or 11.0.0-M2, where the vulnerability has been fixed. No other mitigation or workaround is indicated in the vendor advisory.

Description

CVE-2026-111262 is an LDAP Injection vulnerability in the Jakarta Security LDAP identity store component of Apache TomEE. It occurs because special characters in the caller name are not neutralized before being used in LDAP directory queries. This flaw allows a remote unauthenticated attacker to manipulate LDAP queries to enumerate accounts, infer directory attribute values, or affect login validation. The issue affects only applications using the LDAP identity store. Upgrading to Apache TomEE versions 10.3.0 or 11.0.0-M2 resolves the vulnerability.

Impact

An attacker can remotely exploit this vulnerability without authentication to manipulate LDAP queries. This can lead to unauthorized enumeration of user accounts, disclosure of directory attribute values, and potentially bypass or influence authentication mechanisms. The impact is limited to applications that use the LDAP identity store component of Apache TomEE.

Summary

The Jakarta Security LDAP identity store in Apache TomEE does not properly sanitize special characters in the caller name before incorporating it into LDAP queries. This lack of input neutralization enables remote unauthenticated attackers to perform LDAP Injection attacks, potentially enumerating user accounts, extracting directory attribute information, or influencing authentication logic by altering which directory entry is validated during login. The vulnerability affects Apache TomEE versions prior to 10.3.0 and 11.0.0-M2. The vendor has fixed the issue in versions 10.3.0 and 11.0.0-M2.

CWE-90Improper Neutralization of Special Elements used in an LDAP Query (LDAP Injection) (opens in a new tab)
Base weaknessOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an LDAP query using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended LDAP query when it is sent to a downstream component.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
LDAP Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.7 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
LDAP Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

lists.apache.org/thread.html/qrfq68g2znq773z7g960qsckldvtkqzd (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Nov 2026, 15:21 UTC

WeaknessesCWE-90

Technical details

References

Community reviews

Related threats