Quick answers
- Is CVE-2026-111261 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111261 being exploited in the wild.
- How severe is CVE-2026-111261?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Apache Jakarta Security before 10.3.0 and before 11.0.0-M2.
- Is there a fix for CVE-2026-111261?
- Yes: fixed in 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-111261 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-111261?
- Check whether you run Apache Jakarta Security 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: 10.3.0, 11.0.0-M2
Technical details
The vulnerability exists in the LDAP identity store's password validation logic. When a directory server allows unauthenticated binds (a common default configuration), supplying an empty password succeeds, enabling account takeover. The flaw is a logic error in authentication handling that fails to reject empty passwords before attempting the bind operation.
Affected products
- Apache Jakarta Security before 10.3.0 and before 11.0.0-M2
Timeline
- 2026-11-10: disclosed