HCL
HCL MyXalytics
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2025-52655 | 10 Oct 2025 | HCL MyXalytics: 6.6 | As a part of HCL MyXalytics v6.7, these issues have been remediated. For customers using older versions, the mitigation path will include upgrade to version 6.7 which in turn will fix the vulnerabilities during upgrade process. For fix implementation, our HCL MyXalytics support team will provide required the assistance. | Update reference ↗ |
| CVE-2025-52656 | 3 Oct 2025 | HCL MyXalytics: 6.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-52653 | 3 Oct 2025 | HCL MyXalytics: 6.6 | For customers using older version, mitigation path will include upgrade to version 6.7 which in turn will fix the vulnerability during upgrade process | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.