Pre-authentication unsafe deserialization in IBM WebSphere Application Server can bypass authentication or execute arbitrary code

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-14512?

CVE-2026-14512 is a vulnerability classified as Deserialization of Untrusted Data, affecting WebSphere Application Server (affected versions: 9.0 and 8.5). This vulnerability is rated Critical, with a CVSS score of 9.8. Current sources do not report this vulnerability as exploited.

Overview

Original source data

IBM WebSphere Application Server 9.0, and 8.5 traditional is vulnerable to pre-authentication unsafe deserialization which could allow a remote attacker to bypass authentication or execute arbitrary code.

Affected products and scope

IBM WebSphere Application Server traditional is identified by IBM as affected in the following branches:

  • Branch 9.0.0.0 through 9.0.5.28 is affected. IBM lists Fix Pack 9.0.5.29 or later as the fix-pack path, with targeted availability in 3Q2026.
  • Branch 8.5.0.0 through 8.5.5.30 is affected. IBM lists Fix Pack 8.5.5.31 or later as the fix-pack path, with targeted availability in 3Q2026.
  • The interim fix for APAR PH72166 is listed for releases 9.0.5.20 through 9.0.5.28 and 8.5.5.25 through 8.5.5.30.
  • IBM notices also identify related deployment contexts including IBM Cloud Pak for Applications 5.1, 5.2, and 5.3; Jazz for Service Management 1.1.3.7 through 1.1.3.27; and IBM WebSphere Remote Server 8.5, 9.0, and 9.1, because those products use or bundle affected WebSphere Application Server. Releases or parallel branches not explicitly covered should not be treated as confirmed unaffected.

Technical details

The flaw is in the handling of data that is deserialized by IBM WebSphere Application Server traditional before authentication is completed. Attacker-controlled input can reach this processing path without an account, potentially resulting in authentication bypass or arbitrary code execution. The record establishes network reachability, no required privileges, no user interaction, and low attack complexity. The available evidence does not identify the specific endpoint, serialized object format, Java class, or payload involved. An exact endpoint or exploit chain should therefore not be inferred beyond the documented pre-authentication unsafe deserialization mechanism.

Exploitability

The vulnerability is remotely reachable over the network before authentication, with no prior privileges and no user interaction required. The record characterizes the attack as low complexity, so a suitably crafted request may be sufficient to trigger the vulnerable path when the relevant server interface is exposed. The supplied record marks public_exploit as false, but it does not establish the actual exploitation status. The known-exploited and ransomware-campaign fields are unset, so they do not support a conclusion that exploitation has not occurred.

Technical impact

Successful exploitation could provide unauthorized access through authentication bypass or arbitrary code execution on the WebSphere server. The practical result depends on the server process privileges, configuration, and deployed applications, but may affect application data, application functions, and service availability. The supplied assessment characterizes the potential impact as high across confidentiality, integrity, and availability, but it does not identify a specific operating-system privilege level for executed code. The available evidence does not establish a particular compromise or actual impact scope.

Business impact

Successful exploitation could let an attacker bypass application authentication or execute code on a WebSphere server. Depending on the process privileges and deployment configuration, this could enable unauthorized access to application functions and data, data modification, or service disruption. The potential consequences span confidentiality, integrity, and availability. The available evidence does not identify a specific compromise, victim, or accessed dataset.

Remediation

  1. For WebSphere Application Server traditional 9.0.0.0 through 9.0.5.28, upgrade to the minimum fix pack required by the interim fix and then apply the interim fix that resolves APAR PH72166. IBM lists 9.0.5.20-WS-WAS-IFPH72166 for releases 9.0.5.20 through 9.0.5.28.
  2. For WebSphere Application Server traditional 8.5.0.0 through 8.5.5.30, upgrade to the minimum fix pack required by the interim fix and then apply the interim fix that resolves APAR PH72166. IBM lists 8.5.5.25-WS-WAS-IFPH72166 for releases 8.5.5.25 through 8.5.5.30.
  3. The fix-pack alternatives are Fix Pack 9.0.5.29 or later for the 9.0 branch, or Fix Pack 8.5.5.31 or later for the 8.5 branch, subject to IBM's stated targeted availability.
  4. Check IBM's interim-fix page for additional packages applicable to the platform and current fix-pack level. After updating, verify in inventory that APAR PH72166 is addressed on every instance and IBM product that uses WebSphere.
  5. IBM does not provide a workaround or mitigation for this vulnerability. A general operational control should not be treated as a substitute for the specified interim fix or fix pack.

Detection

  1. Inventory all IBM WebSphere Application Server traditional instances, including IBM products that bundle or deploy WebSphere as a supporting component, and compare each installation with the affected branches.
  2. Check IBM Installation Manager, deployment records, and change records to confirm that the interim fix resolving APAR PH72166 is installed on every relevant instance.
  3. Identify instances whose pre-authentication WebSphere interfaces are reachable from untrusted networks. The available evidence does not name a specific endpoint, so review should not be limited to an unconfirmed path.
  4. After identifying exposed instances, review authentication activity and server activity for anomalies. This is precautionary monitoring, not a vendor-published IOC.
  5. Do not treat the absence of suspicious log activity as proof of safety. Confirm the installed release and fix state directly.
Sources (17)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.