Skip to main content
VulnerabilityPublished Updated

CVE-2025-36038: IBM WebSphere Application Server · Deserialization of Untrusted Data

Affects IBM WebSphere Application ServerSource CVE Database V5

0

Not known to be exploited · 13% EPSS · CVSS 9.0 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
13.3% chance of exploitation in 30 days – higher than 96% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Mavencom.ibm.websphere/websphere-application-serverpkg:maven/com.ibm.websphere/websphere-application-serverOther threatsAffected
  • =8.5
  • =9.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Apply official patches from IBM as soon as they are released to address CVE-2025-36038. Monitor IBM security advisories closely for updates.
  2. Until patches are available, restrict network access to WebSphere Application Server management and administrative interfaces using firewalls, VPNs, or network segmentation to limit exposure to untrusted networks.
  3. Implement strict input validation and deserialization controls where possible, including disabling or restricting deserialization of untrusted data in application code and middleware configurations.
  4. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious serialized object payloads targeting WebSphere endpoints.
  5. Monitor logs and network traffic for anomalous activity indicative of exploitation attempts, such as unusual serialized object sequences or unexpected remote code execution indicators.
  6. Conduct regular security assessments and penetration testing focusing on deserialization vulnerabilities and middleware security.
  7. Educate development and operations teams about secure deserialization practices and the risks associated with untrusted data processing.
  8. Consider deploying runtime application self-protection (RASP) solutions to detect and prevent exploitation attempts in real time.
  9. Maintain an incident response plan tailored to middleware compromise scenarios to enable rapid containment and recovery.

Description

IBM WebSphere Application Server 8.5 and 9.0 could allow a remote attacker to execute arbitrary code on the system with a specially crafted sequence of serialized objects.

References

Community reviews

Loading reviews…