Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to HCL MyCloud with low-privilege credentials
-
ExploitNavigate to or trigger endpoint that returns license key in HTTP response
-
ExecutionCapture key via browser proxy or developer tools
-
ImpactUse extracted key to activate unauthorized HCL MyCloud deployments
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an active authenticated session with at least low-privilege access to HCL MyCloud (PR:L per CVSS vector) - unauthenticated attackers cannot exploit this. The CVSS AC:H rating indicates that specific conditions beyond authentication must be met to trigger the response containing the license key, likely requiring knowledge of or access to a particular endpoint, workflow step, or application state. The application must be reachable over the network (AV:N). Scope is unchanged (S:U), meaning a successful attacker cannot directly leverage the license key to pivot into other systems or escalate beyond the HCL licensing context. Integrity and availability are unaffected. The key limiting factors are the authentication prerequisite and the high attack complexity, which together substantially reduce realistic exploitation risk compared to the network-accessible exposure surface. |
| Impact | The CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N) scores this at 3.1 (Low), and the signal set corroborates a genuinely low-priority issue. Attack complexity is rated High (AC:H), meaning exploitation is not trivially repeatable and requires specific conditions - likely triggering or intercepting a particular HTTP response path - beyond merely being authenticated. The privilege requirement (PR:L) confirms that unauthenticated exploitation is not possible. The confidentiality impact is limited (C:L) to the license key itself; there is no integrity or availability impact (I:N/A:N) and no scope change (S:U). No EPSS data is available for this CVE, the issue does not appear in the CISA KEV catalog, and no public exploit code has been identified. The primary real-world consequence is license abuse or unauthorized activation of HCL software, not direct system compromise. This is a compliance and licensing integrity concern rather than an exploitation-priority vulnerability. |
| Exploit ScenarioDerived | An authenticated low-privilege user logs into HCL MyCloud and, using a browser proxy tool such as Burp Suite or browser developer tools, captures HTTP responses during normal application interaction. A specific response - likely from a settings, licensing, or status endpoint - returns the product license key in plaintext. The user extracts the key and uses it to activate an unauthorized instance of HCL MyCloud or a related HCL product, bypassing licensing costs without public exploit tooling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 21, 2026
HCL MyCloud leaks license keys in HTTP responses, enabling authenticated low-privilege users who can observe or intercept the relevant response to capture and misuse the exposed key material. All versions appear affected per CPE wildcard data (cpe:2.3:a:hclsoftware:mycloud:*:*:*:*:*:*:*:*), and the vulnerability is vendor-confirmed via HCL advisory KB0132381. No public exploit code has been identified and the issue is not listed in the CISA KEV catalog, placing overall risk at low severity consistent with the CVSS 3.1 score of 3.1.
RemediationAI
Consult the HCL vendor advisory KB0132381 at https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0132381 for the official patch or update guidance, as no specific fixed version is confirmed in the available data. Upstream fix availability and exact patch version are not independently verifiable from current data - treat any version information from the advisory as the authoritative source. As compensating controls pending patching, restrict HCL MyCloud access to only authorized, role-appropriate users and avoid exposing the application directly to untrusted networks. Review HTTP response content for license key material and, where application architecture permits, mask or omit such values from client-facing responses. Rotate any exposed license keys after patching to limit residual risk from keys that may have already been captured.
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
HCL MyCloud is an enterprise cloud management platform from HCL Software. The root cause maps to CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), a class of flaw where an application returns sensitive runtime data - in this case license key material - in HTTP response payloads without masking or filtering. The CPE entry cpe:2.3:a:hclsoftware:mycloud:*:*:*:*:*:*:*:* applies a wildcard across all versions, suggesting the exposure is present in the application's response-handling logic rather than a version-specific regression. License keys in enterprise software typically control feature entitlements and activation, so their exposure can enable unauthorized product activation, license cloning, or intelligence gathering about the deployment's commercial configuration.
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:H/PR:L/UI:N/S:U/C:L/I:N/A:N
Network-reachable but requires authenticated low-privilege access and specific conditions (AC:H) to trigger the key-exposing response; confidentiality impact is limited to license key material with no integrity or availability effect.
Primary rating from Vendor (HCL).
CVSS VectorVendor: HCL
DescriptionCVE.org
HCL MyCloud was affected with License Key Revealed in HTTP Response. It may enable attackers to misuse the exposed information and compromise the application's security.
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.
Weak password policy enforcement in HCL MyCloud exposes authenticated accounts to brute-force and credential-stuffing at
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-46342
GHSA-c2v7-9cvc-gh5m
NVD
CVE.org
EPSS
VulDB
Exploit-DB