Quick answers
- Is CVE-2026-111260 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111260 being exploited in the wild.
- How severe is CVE-2026-111260?
- 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-111260?
- 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-111260 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-111260?
- 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 stems from using insufficiently entropic, non-cryptographic random number generation for OpenID Connect state and nonce parameters. An attacker who can predict these values can forge authentication callbacks, enabling account takeover via impersonation and weakening ID token replay protection. The vulnerability affects the OpenID Connect authentication mechanism and is exploitable remotely without authentication.
Affected products
- Apache Jakarta Security before 10.3.0 and before 11.0.0-M2
Timeline
- 2026-11-10: disclosed