Skip to main content
CVE-2025-36072VulnerabilityPublished

CVE-2025-36072: IBM webMethods Integration · Deserialization of Untrusted Data

Affects IBM webMethods IntegrationSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
IBM webMethods IntegrationAffected
  • =10.11
  • =10.15
  • =11.1
Fixed in–

AI-suggested

1. Apply official IBM patches or updates as soon as they become available to remediate the vulnerability at the source. 2. Restrict access to IBM webMethods Integration consoles and interfaces to only trusted and necessary personnel, enforcing the principle of least privilege. 3. Implement strong authentication mechanisms, including multi-factor authentication (MFA), to reduce the risk of credential compromise. 4. Employ network segmentation to isolate integration servers from less trusted network zones, limiting potential lateral movement. 5. Monitor logs and network traffic for unusual deserialization activity or anomalous commands indicative of exploitation attempts. 6. Conduct regular security audits and penetration testing focused on deserialization vulnerabilities and access controls within integration environments. 7. Educate administrators and developers about secure coding practices related to serialization and deserialization processes. 8. Consider deploying application-layer firewalls or runtime application self-protection (RASP) solutions that can detect and block malicious deserialization payloads. 9. Review and harden configuration settings of IBM webMethods Integration to disable or restrict unnecessary deserialization features where possible.

Description

IBM webMethods Integration 10.11 through 10.11_Core_Fix22, 10.15 through 10.15_Core_Fix22, and 11.1 through 11.1_Core_Fix6 IBM webMethods Integration allow an authenticated user to execute arbitrary code on the system, caused by the deserialization of untrusted object graphs data.

References

Community reviews

Loading reviews…