Quick answers
- Is CVE-2026-93909 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93909 being exploited in the wild.
- How severe is CVE-2026-93909?
- Critical severity, with a CVSS score of 9.1, published 13 October 2026.
- Which products and versions are affected?
- IBM WebSphere Application Server Liberty 17.0.0.3 through 26.0.0.10.
- Is there a fix for CVE-2026-93909?
- Yes: fixed in WebSphere Application Server Liberty 26.0.0.11 or later; interim fix for APAR DT502359. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93909 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-93909?
- Check whether you run IBM WebSphere Application Server Liberty 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: WebSphere Application Server Liberty 26.0.0.11 or later; interim fix for APAR DT502359
Technical details
The vulnerability is a session fixation flaw (CWE-384) in the samlWeb-2.0 feature of WebSphere Liberty that allows authentication bypass via the network with no privileges or user interaction required. When this SAML authentication component is enabled, an attacker can exploit the session handling mechanism to gain unauthorized access to applications. A fix is available in Liberty Fix Pack 26.0.0.11 and later, or via interim fix for earlier versions.
Affected products
- IBM WebSphere Application Server Liberty 17.0.0.3 through 26.0.0.10
Timeline
- 2026-10-13: disclosed