Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessEnumerate valid MyCloud usernames
-
DeliveryCompile credential list (dictionary or breach data)
-
ExploitSubmit automated login attempts
-
ExecutionAuthenticate with weak/matching password
-
ImpactAccess victim cloud workspace
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Password strength requirements
|
| Exploitation Conditions | Exploitation requires network-level access to the HCL MyCloud login interface and knowledge of valid usernames or email addresses registered on the platform. The attack is constrained by any rate-limiting, CAPTCHA, or account lockout mechanisms the deployment may have in place - the advisory does not confirm whether such controls exist by default. The vendor CVSS vector assigns AC:H and PR:L, suggesting HCL considers this non-trivial to exploit and that some level of existing access or account knowledge is required; however, this contrasts with the typical brute-force threat model where PR:N is standard. Exploitation is limited to environments where strong password policies and MFA are not enforced externally (e.g., via an IdP or SSO layer). The vulnerability does NOT affect deployments where authentication is delegated entirely to an external identity provider that enforces its own password policy. |
| Impact | The vendor-supplied CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L, score 3.1) presents several notable inconsistencies worth flagging for security teams. First, PR:L implies the attacker already holds low-privilege credentials - but the core threat of a weak password policy is enabling unauthorized acquisition of credentials, making PR:N more appropriate for the attacker's initial position. Second, the impact metrics C:N and I:N but A:L are counterintuitive: successful credential attacks primarily threaten confidentiality and integrity (account data, stored content), not availability. No EPSS score was provided, and this CVE is not listed in the CISA KEV catalog. No POC is known. Real-world risk is moderate-to-low given the niche deployment footprint of HCL MyCloud, but organizations using the platform should treat credential-based attack surface seriously regardless of the low CVSS score, as weak password policies are a reliable enabler of account takeover in any cloud application. |
| Exploit ScenarioDerived | An attacker targeting a known HCL MyCloud user account obtains a list of commonly used passwords or previously leaked credential pairs and submits automated login requests against the MyCloud authentication endpoint. Because the platform does not enforce strong password requirements, a significant fraction of accounts may use short or dictionary-based passwords, allowing the attacker to gain unauthorized access to a user's cloud workspace and any data or files stored therein. No public exploit code or tooling specific to this CVE is known at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 21, 2026
Weak password policy enforcement in HCL MyCloud exposes authenticated accounts to brute-force and credential-stuffing attacks, potentially enabling unauthorized account takeover. The flaw is classified under CWE-521 (Weak Password Requirements), meaning the platform fails to enforce sufficient password strength constraints on users. Despite tags indicating Information Disclosure risk, no public exploit code or active exploitation has been identified at time of analysis, and the vendor-assigned CVSS score of 3.1 reflects a Low severity rating.
RemediationAI
Consult the HCL Software advisory at https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0132381 for vendor-released guidance; an exact patched version is not independently confirmed from available data. As compensating controls, administrators should enforce a strong password policy at the platform or identity provider level - requiring minimum length (12+ characters), character complexity, and rejection of common/dictionary passwords. Enabling multi-factor authentication (MFA) is the highest-impact mitigation, as it renders brute-forced credentials alone insufficient for login; however, MFA may add friction for end users and requires rollout planning. Account lockout policies (e.g., lockout after 5-10 failed attempts) should be configured to throttle brute-force attempts, with the trade-off that overly aggressive lockout thresholds can enable denial-of-service against accounts. Credential monitoring via integration with breach databases (e.g., HaveIBeenPwned API) can detect compromised passwords proactively.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-521 (Weak Password Requirements) describes a class of weakness where a software product does not enforce adequate password strength policies - such as minimum length, character complexity, or restrictions on common/dictionary passwords. The affected product, HCL MyCloud (CPE: cpe:2.3:a:hclsoftware:mycloud:*:*:*:*:*:*:*:*), is a cloud-based collaboration platform developed by HCL Software. A lax password policy enables attackers to target accounts using automated brute-force tools or credential lists from prior breaches (credential stuffing), reducing the effort required to successfully authenticate as a legitimate user. The asterisk wildcard in the CPE version field indicates all known versions are potentially affected.
Know when Mycloud gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Brute-force against a login endpoint requires no prior privileges and low complexity; successful exploitation impacts confidentiality and integrity, not availability.
Primary rating from Vendor (HCL).
CVSS VectorNVD
Lifecycle Timeline
2DescriptionNVD
HCL MyCloud was affected with Weak Password Policy. It may increase the risk of account compromise through brute-force or credential-based attacks.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
HCL MyCloud leaks license keys in HTTP responses, enabling authenticated low-privilege users who can observe or intercep
Concurrent Login Vulnerability in HCL MyCloud permits authenticated users to sustain multiple simultaneous active sessio
TLS session confidentiality in HCL MyCloud is undermined by the LUCKY13 padding oracle vulnerability, enabling a network
Session cookie exposure in HCL MyCloud arises from the cookie Path attribute not being set, causing authentication token
HCL MyCloud ships a bundled IIS Server component containing publicly disclosed vulnerabilities, classified under CWE-110
Server version disclosure in HCL MyCloud exposes software version strings - likely via HTTP response headers or applicat
EUVD-2026-46340
GHSA-hhgc-cpmc-3r4j
NVD
CVE.org
EPSS
VulDB
Exploit-DB