CVE-2025-36093VulnerabilityPublished 3 Nov 2025

CVE-2025-36093: IBM Cloud Pak For Business Automation · Client-Side Enforcement of Server-Side Security

Affects IBM Cloud Pak For Business AutomationSource CVE Database V5

Not known to be exploited · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 18% 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:U/C:L/I:L/A:N

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

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Nov 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
IBM Cloud Pak For Business Automation	Affected =25.0.0 =24.0.1 =24.0.0	Fixed in–

AI-suggested

1. Monitor IBM security advisories closely for official patches addressing CVE-2025-36093 and apply them promptly once available. 2. Until patches are released, enforce strict network segmentation and use encrypted, authenticated communication channels (e.g., TLS with certificate pinning) to mitigate man-in-the-middle attack vectors. 3. Implement network intrusion detection and prevention systems (IDS/IPS) to detect anomalous traffic patterns indicative of MitM attempts. 4. Review and harden access control policies within IBM Cloud Pak configurations to minimize exposure of sensitive endpoints. 5. Conduct regular security assessments and penetration tests focusing on client-server communication security to identify potential weaknesses. 6. Educate system administrators and security teams about the risks of client-side enforcement of security controls and promote best practices for server-side validation. 7. Consider deploying endpoint security solutions that can detect and block MitM tools or suspicious network activities. 8. Restrict administrative access to IBM Cloud Pak consoles to trusted networks and VPNs to reduce attack surface.

Description

IBM Cloud Pak For Business Automation 25.0.0, 24.0.1, and 24.0.0 could allow an attacker to access unauthorized content or perform unauthorized actions using man in the middle techniques due to improper access controls.

Impact

For European organizations, the vulnerability poses a risk of unauthorized data exposure and manipulation within IBM Cloud Pak For Business Automation environments. This can lead to leakage of sensitive business automation workflows, intellectual property, or confidential operational data. Integrity compromise could allow attackers to alter automation processes, potentially disrupting business operations or causing incorrect processing outcomes. Although the attack complexity is high and no exploits are currently known, the network-based nature of the attack means that organizations with exposed or poorly segmented networks are at higher risk. Given the critical role of IBM Cloud Pak in automating business processes, any compromise could have cascading effects on compliance, operational continuity, and trust. European entities in finance, manufacturing, and government sectors using this product may face regulatory scrutiny if unauthorized access leads to data breaches. The medium severity rating suggests moderate urgency but does not indicate immediate critical risk.

CWE-602Client-Side Enforcement of Server-Side Security (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product is composed of a server that relies on the client to implement a mechanism that is intended to protect the server.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely.
Architecture and Design
If some degree of trust is required between the two entities, then use integrity checking and strong authentication to ensure that the inputs are coming from a trusted source.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.1 (opens in a new tab)
V1.5.3 (opens in a new tab)
V4.1.1 (opens in a new tab)
Attack patterns
Manipulating Hidden Fields (opens in a new tab)
Create Malicious Client (opens in a new tab)
Removing Important Client Functionality (opens in a new tab)
Removing/short-circuiting 'Purse' logic: removing/mutating 'cash' decrements (opens in a new tab)
Accessing/Intercepting/Modifying HTTP Cookies (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7249999 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 16:14 UTC

WeaknessesCWE-602

Technical details

References

Community reviews

Related threats