Skip to main content

IBM WebSphere Liberty CVE-2026-93909

| EUVDEUVD-2026-100498 CRITICAL
Session Fixation (CWE-384)
2026-10-13 psirt@us.ibm.com GHSA-vcr6-887c-vp66
9.1
CVSS 3.1 · Vendor: us
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify Liberty host with samlWeb-2.0 enabled
  2. Delivery
    Plant or fix a known session identifier
  3. Exploit
    Induce/await victim SAML authentication
  4. Execution
    Hijack authenticated session
  5. Impact
    Access protected resources as victim

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V7 - Session Management Session fixation prevention
Exploitation Conditions

Exploitation requires that the target IBM WebSphere Application Server Liberty instance (versions 17.0.0.3 through 26.0.0.10) has the samlWeb-2.0 feature explicitly enabled in its server configuration to provide SAML 2.0 web single sign-on - this is an opt-in feature, not a default, so deployments without SAML SSO configured are not affected. Per the supplied CVSS vector the network path needs no attacker authentication or privileges (PR:N) and no user interaction (UI:N); however, because the underlying weakness is CWE-384 Session Fixation, realistic exploitation typically depends on a legitimate user subsequently authenticating via SAML against an attacker-influenced session, which is a practical limiting factor defenders should weigh against the raw vector. Patch level of the running Liberty instance also limits exposure.

Impact

This is a high-priority vulnerability on technical merits. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N, base 9.1) describes a network-reachable, low-complexity authentication bypass requiring no privileges and no user interaction, yielding high confidentiality and integrity impact - consistent with an attacker gaining access to protected resources as another principal. However, several real-world risk signals are MISSING from the input and must not be assumed: no EPSS score is provided, there is no CISA KEV listing, and no proof-of-concept or exploit code is referenced, so exploitation is 'no public exploit identified at time of analysis.' A notable tension exists between the CVSS vector and the vulnerability nature: CWE-384 (Session Fixation) and the 'Session Fixation' tag typically require tricking or waiting for a legitimate user to authenticate against an attacker-influenced session identifier, which in practice often implies some victim interaction - yet the vector states UI:N. This should be verified against the IBM advisory, as it materially affects whether exploitation is fully unauthenticated-and-automatable or requires a victim to log in. Additionally, exploitation is gated on the samlWeb-2.0 feature being enabled, which is a non-default deployment condition that narrows the exposed population below the raw 9.1 severity.

Exploit ScenarioDerived

An attacker targets an internet-facing IBM WebSphere Liberty server that has the samlWeb-2.0 SAML single sign-on feature enabled, and abuses the authentication/session handling flaw to bypass authentication and obtain access as a legitimate user without valid credentials. Given CWE-384 (Session Fixation), the attacker likely plants or fixes a session identifier and then leverages a victim's subsequent SAML login to hijack that authenticated session. No public exploit code is referenced in the provided data.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 13, 2026

Authentication bypass in IBM WebSphere Application Server - Liberty (17.0.0.3 through 26.0.0.10) allows remote, unauthenticated attackers to subvert the SAML 2.0 web single sign-on flow when the samlWeb-2.0 feature is explicitly enabled, resulting in a session fixation condition that yields high confidentiality and integrity impact with no availability impact (CVSS 3.1 base 9.1, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N). Because samlWeb-2.0 is an opt-in Liberty feature rather than a default, only deployments that have configured SAML SSO are in scope; in practice exploitation is most credible when a legitimate user subsequently authenticates through an attacker-influenced session, which is a practical limiting factor relative to the raw vector. There is no public exploit identified at time of analysis, no confirmed active exploitation (no CISA KEV listing), and no EPSS score was supplied with the available intelligence.

RemediationAI

No exact fix version is provided in the available intelligence, so treat IBM Support document https://www.ibm.com/support/pages/node/7292236 as the authoritative source and apply the interim fix or fix-pack level IBM designates there, moving any Liberty instance in the 17.0.0.3 through 26.0.0.10 band to a release at or above the corrected level IBM publishes. If the samlWeb-2.0 feature is not required, the most direct compensating control is to disable it (remove samlWeb-2.0 from the configured feature list and restart the server), which fully removes the attack surface but breaks SAML 2.0 web SSO for that instance, so that step should be validated against business dependencies first. Where SAML SSO must remain enabled and patching must be deferred, reduce exposure by invalidating and reissuing session identifiers at the SAML authentication boundary - ensuring the post-assertion session is newly created rather than a continuation of any pre-authentication session - and by tightening network access to the SAML assertion consumer service endpoints to trusted identity-provider sources only; each of these is a partial mitigation that reduces, but does not eliminate, the fixation path and requires application-level verification because the flaw is in the product's session handling. Given the 9.1 severity and the high confidentiality and integrity ratings, prioritize inventorying Liberty instances with samlWeb-2.0 enabled and schedule remediation ahead of routine maintenance; note that no public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, so urgency is driven by technical severity and the opt-in exposure profile rather than by observed attacks.

Affected VersionsENISA

WebSphere Application Server - Liberty 17.0.0.3 ≤26.0.0.10

Affected Packages

euvd websphere_application_server_liberty no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The weakness is CWE-384 (Session Fixation) in the SAML 2.0 web SSO implementation of IBM WebSphere Application Server - Liberty, exposed through the samlWeb-2.0 feature that administrators enable in server configuration (server.xml feature manager) to provide SAML-based web single sign-on. In a session fixation attack against a federated SSO flow, an attacker who can establish, predict, or otherwise influence a session identifier before the victim authenticates can arrange for the victim's SAML assertion to be bound to that pre-existing session; once the identity provider posts the assertion back to the service provider and the session is elevated to authenticated, the attacker retains the same session handle and inherits the victim's authenticated context. The assessed vector confirms a network-reachable, unauthenticated path with no user interaction (PR:N/UI:N), and the high integrity and confidentiality ratings reflect that a hijacked session can both read protected data and act under the victim's identity, while the unchanged scope and absent availability impact indicate the compromise stays within the Liberty security context and does not itself deny service. IBM PSIRT is the reporting party, the vulnerability is catalogued as ENISA EUVD-2026-100498, and the supplied CPE/affected-version data covers the Liberty 17.0.0.3 through 26.0.0.10 range with the SAML feature active.

Know when Session Fixation gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (us) PRIMARY 9.1 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
vuln.today AI 9.1 CRITICAL

Network-reachable SAML endpoint, no attacker credentials or privileges (PR:N), bypass grants access as another user (C:H/I:H); availability unaffected (A:N); UI:N retained per input though session fixation may warrant UI:R.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (us).

CVSS VectorVendor: us

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

DescriptionCVE.org

IBM WebSphere Application Server - Liberty 17.0.0.3 through 26.0.0.10 is vulnerable by an authentication bypass vulnerability when samlWeb-2.0 feature is enabled.

Executive ViewAI

Why It Matters

IBM WebSphere Application Server - Liberty deployments that have enabled the SAML 2.0 web single sign-on feature are affected by a critical authentication bypass (CVE-2026-93909) that could allow unauthenticated attackers to hijack user sessions, leading to unauthorized access to sensitive data and potential integrity compromise. Although only organizations using SAML SSO are in scope, the high confidentiality and integrity impact means that successful exploitation could undermine trust in the authentication mechanism and expose critical business applications. With no public exploit identified at time of analysis and no vendor-released patch identified at time of analysis, leadership should prioritize identifying affected systems and implementing interim mitigations to reduce risk.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include disabling the samlWeb-2.0 feature if not required, enforcing multi-factor authentication, monitoring for session fixation indicators, and implementing network-level protections.

Threat Intelligence Overview

EPSS Score
0.4%
Top 73% exploitable
Prevalence
High
widely deployed enterprise Java application server, but SAML feature is optional
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Total

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2026-102489 CRITICAL POC
9.4 Sep 30

Session hijacking in self-hosted Zammad 6.3.0 through 6.5.4 allows remote, unauthenticated attackers to take over a legi

CVE-2017-12965 CRITICAL POC
9.8 Aug 23

Session fixation vulnerability in Apache2Triad 1.5.4 allows remote attackers to hijack web sessions via the PHPSESSID pa

CVE-2025-28242 CRITICAL POC
9.8 Apr 18

Improper session management in the /login_ok.htm endpoint of DAEnetIP4 METO v1.25 allows attackers to execute a session

CVE-2022-40916 CRITICAL POC
9.8 Feb 06

Tiny File Manager v2.4.7 and below is vulnerable to session fixation. Rated critical severity (CVSS 9.8), this vulnerabi

CVE-2025-45949 CRITICAL POC
9.8 Apr 28

A critical vulnerability was found in PHPGurukul User Registration & Login and User Management System V3.3 in the /login

CVE-2023-48929 CRITICAL POC
9.8 Dec 08

Franklin Fueling Systems System Sentinel AnyWare (SSA) version 1.6.24.492 is vulnerable to Session Fixation. Rated criti

CVE-2023-41012 CRITICAL POC
9.8 Sep 05

An issue in China Mobile Communications China Mobile Intelligent Home Gateway v.HG6543C4 allows a remote attacker to exe

CVE-2023-31498 CRITICAL POC
9.8 May 11

A privilege escalation issue was found in PHP Gurukul Hospital Management System In v.4.0 allows a remote attacker to ex

CVE-2022-3269 CRITICAL POC
9.8 Sep 23

Session Fixation in GitHub repository ikus060/rdiffweb prior to 2.4.7. Rated critical severity (CVSS 9.8), this vulnerab

CVE-2021-39290 CRITICAL POC
9.8 Aug 23

Certain NetModule devices allow Limited Session Fixation via PHPSESSID. Rated critical severity (CVSS 9.8), this vulnera

CVE-2020-11729 CRITICAL POC
9.8 Apr 15

An issue was discovered in DAViCal Andrew's Web Libraries (AWL) through 0.60. Rated critical severity (CVSS 9.8), this v

CVE-2019-18418 CRITICAL POC
9.8 Oct 24

clonos.php in ClonOS WEB control panel 19.09 allows remote attackers to gain full access via change password requests be

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy