CVE-2025-62330: HCL Software DevOps Deploy · Cleartext Transmission
Affects HCL Software DevOps DeploySource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% 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 16 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| HCL Software DevOps Deploy | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-62330, organizations should immediately audit their HCL DevOps Deploy installations to identify if HTTP ports are open and accessible. The primary mitigation is to disable HTTP access entirely or configure the system to enforce HTTPS with automatic redirection from HTTP to HTTPS, ensuring all sensitive data is encrypted in transit. Network segmentation should be applied to restrict access to the DevOps Deploy server only to trusted hosts and networks. Implementing strong network monitoring and intrusion detection can help identify suspicious MITM or interception attempts. Organizations should also verify that TLS configurations follow best practices, including using up-to-date certificates and disabling weak protocols or ciphers. If patches or updates become available from HCL Software addressing this issue, they should be applied promptly. Additionally, educating DevOps teams about secure configuration and monitoring for unusual authentication or session activity can reduce risk. Finally, consider deploying VPNs or zero-trust network access solutions to further protect communication channels.
Description
HCL DevOps Deploy is susceptible to a cleartext transmission of sensitive information because the HTTP port remains accessible and does not redirect to HTTPS as intended. As a result, an attacker with network access could intercept or modify user credentials and session-related data via passive monitoring or man-in-the-middle attacks.