CVE-2025-13489: UCD – IBM DevOps Deploy · Cleartext Transmission
Affects UCD – IBM DevOps DeploySource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium.
Data as of 26 Oct 2026, 12:29 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% 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:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Dec 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 UCD - IBM DevOps Deploy | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-13489, European organizations should immediately assess their IBM DevOps Deploy 8.1 deployments for exposure to unencrypted network traffic. Specific recommendations include: 1) Enforce the use of TLS or other strong encryption protocols for all communications involving IBM DevOps Deploy components, ensuring that no sensitive data is transmitted in cleartext. 2) Implement strict network segmentation and isolate deployment infrastructure from untrusted networks to reduce the risk of MitM attacks. 3) Use VPNs or secure tunnels for remote access to deployment environments. 4) Monitor network traffic for signs of interception or anomalous activity indicative of MitM attempts. 5) Regularly update and patch IBM DevOps Deploy as vendor fixes become available, even though no patches are currently listed. 6) Review and harden configuration settings to disable any legacy or insecure protocols. 7) Educate DevOps and security teams about the risks of cleartext transmission and best practices for securing deployment pipelines. 8) Conduct penetration testing focusing on network interception vulnerabilities to validate mitigations. These steps go beyond generic advice by focusing on encryption enforcement, network architecture, and proactive detection tailored to the specific deployment context of IBM DevOps Deploy.
Description
IBM UCD - IBM DevOps Deploy 8.1 through 8.1.2.3 IBM DevOps Deploy transmits data in clear text that could allow an attacker to obtain sensitive information using man in the middle techniques.