Skip to main content
CVE-2025-62329VulnerabilityPublished Updated

CVE-2025-62329: HCL Software DevOps Deploy / Launch · Insufficient Session Expiration

Affects HCL Software DevOps Deploy / LaunchSource CVE Database V5

0

Not known to be exploited · CVSS 5.0 Medium.

Data as of 26 Oct 2026, 06:15 UTC

CVSS 3.1 base score
5.0Medium
How severe the flaw is on the 0–10 CVSS scale.
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:L/UI:N/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Dec 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
HCL Software DevOps Deploy / LaunchAffected
  • >=7.3 <=7.3.2.15
  • >=8.0 <=8.0.1.10
  • >=8.1 <=8.1.2.3
Fixed in–

AI-suggested

1. Apply patches or updates from HCL Software as soon as they become available to address the race condition and improve session expiration handling. 2. Implement network-level controls such as IP address whitelisting, VPN enforcement, or strict firewall rules to limit session access to known, trusted IP addresses. 3. Enhance session monitoring and logging to detect anomalous session reuse patterns, including rapid IP address changes or concurrent sessions from different IPs. 4. Configure session timeouts to be as short as operationally feasible, reducing the window for potential session reuse. 5. Employ multi-factor authentication (MFA) for access to DevOps Deploy / Launch interfaces to add an additional layer of security beyond session tokens. 6. Conduct regular security audits and penetration testing focused on session management and authentication mechanisms. 7. Educate DevOps and security teams about the vulnerability to ensure rapid response and incident handling if suspicious activity is detected. 8. Consider network segmentation to isolate DevOps infrastructure from broader enterprise networks, limiting attacker lateral movement opportunities.

Description

HCL DevOps Deploy / HCL Launch is susceptible to a race condition in http-session client-IP binding enforcement which may allow a session to be briefly reused from a new IP address before it is invalidated. This could lead to unauthorized access under certain network conditions.

References

Community reviews

Loading reviews…