CVE-2025-62327VulnerabilityPublished 7 Jan 2026

CVE-2025-62327: HCLSoftware DevOps Deploy · Insufficiently Protected Credentials

Affects HCLSoftware DevOps DeploySource CVE Database V5

Not known to be exploited · CVSS 4.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.9Medium

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:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
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: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within 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 7 Jan 2026
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.

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
HCLSoftwareDevOps Deploy	Affected =8.1 - 8.1.2.3	Fixed in–

AI-suggested

Until official patches are released, European organizations should implement strict access controls to limit LLM configuration privileges only to trusted administrators. Conduct thorough audits of users with such privileges and monitor their activities for unusual behavior. Encrypt stored credentials using strong cryptographic methods and ensure that credential storage mechanisms follow best practices for secret management. Employ multi-factor authentication (MFA) for accessing DevOps Deploy interfaces to reduce risk from compromised accounts. Regularly review and rotate credentials used in LLM queries to minimize exposure duration. Implement network segmentation to isolate DevOps environments and restrict access to credential stores. Maintain comprehensive logging and alerting to detect any unauthorized attempts to access or retrieve credentials. Engage with HCLSoftware support to obtain patches or updates as soon as they become available and test them in controlled environments before deployment.

Description

CVE-2025-62327 is a medium severity vulnerability in HCL DevOps Deploy versions 8.1 through 8.1.2.3, where users with LLM configuration privileges can recover previously saved credentials used for authenticated LLM queries. The vulnerability stems from insufficient protection of stored credentials (CWE-522). Exploitation requires privileged access but no user interaction and can lead to credential disclosure, impacting confidentiality. There are no known exploits in the wild yet. The CVSS score is 4.9, reflecting a moderate risk primarily due to the need for elevated privileges.

Impact

For European organizations, the primary impact of this vulnerability is the potential compromise of sensitive credentials used in automated DevOps workflows involving LLM queries. Exposure of these credentials could lead to unauthorized access to internal systems or services, undermining confidentiality and potentially enabling further attacks such as privilege escalation or lateral movement. Organizations relying heavily on HCL DevOps Deploy for critical software deployment and automation may face operational risks if attackers exploit this vulnerability. The impact is heightened in sectors where DevOps pipelines integrate with sensitive data or critical infrastructure, such as finance, telecommunications, and government. Since exploitation requires elevated privileges, the threat is mainly from insider threats or attackers who have already gained partial access. However, once credentials are exposed, attackers can bypass authentication mechanisms for LLM queries, potentially extracting sensitive information or manipulating deployment processes. This could result in data breaches, compliance violations under GDPR, and damage to organizational reputation.

CWE-522Insufficiently Protected Credentials (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
Architecture and Design
Use an appropriate security mechanism to protect the credentials.
Architecture and Design
Make appropriate use of cryptography to protect the credentials.
Implementation
Use industry standards to protect the credentials (e.g. LDAP, keystore, etc.).
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V2.10.3 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Signature Spoofing by Key Theft (opens in a new tab)
Password Recovery Exploitation (opens in a new tab)
Kerberoasting (opens in a new tab)
Modify Existing Service (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0127336 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jan 2026, 15:52 UTC

WeaknessesCWE-522

Technical details

References

Community reviews

Related threats