CVE-2025-36037: IBM webMethods Integration · Server-Side Request Forgery (SSRF)
Affects IBM webMethods IntegrationSource CVE Database V5
Not known to be exploited · CVSS 5.4 Medium.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% 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:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| IBM webMethods Integration | Affected
| Fixed in– |
AI-suggested
European organizations should take the following specific mitigation steps: 1) Immediately audit and monitor access to IBM webMethods Integration servers to detect any unusual or unauthorized authenticated activity that could indicate attempts to exploit SSRF. 2) Restrict and harden authentication mechanisms to minimize the risk of credential compromise, including enforcing strong authentication policies and monitoring for compromised accounts. 3) Implement network-level controls such as egress filtering and internal firewall rules to limit the ability of the integration server to make arbitrary outbound requests, thereby reducing the SSRF attack surface. 4) Segregate the integration platform within a dedicated network segment with strict access controls to limit potential lateral movement. 5) Stay in close contact with IBM for official patches or updates addressing CVE-2025-36037 and prioritize timely deployment once available. 6) Conduct penetration testing and vulnerability scanning focused on SSRF vectors within the integration environment to identify and remediate any exploitable configurations. 7) Review and tighten any application-level input validation or request handling configurations that could be abused to trigger SSRF. 8) Maintain comprehensive logging and alerting on outbound requests initiated by the integration platform to detect anomalous behavior early.
Description
IBM webMethods Integration 10.15 and 11.1 is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks.