Quick answers
- Is CVE-2025-52651 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-52651 being exploited in the wild.
- How severe is CVE-2025-52651?
- Low severity, with a CVSS score of 3.5, published 7 September 2026.
- Which products and versions are affected?
- HCL MyXalytics.
- Is there a fix for CVE-2025-52651?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- Am I affected by CVE-2025-52651?
- Check whether you run HCL MyXalytics. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability is a classic input validation flaw in HCL MyXalytics where insufficient sanitization of user-supplied input allows malicious or unexpected data to reach sensitive processing logic. The exact attack vector and preconditions are not fully detailed in the available advisory text, but the vulnerability class suggests inadequate input boundary checking. An attacker can craft specially-formed input to trigger unintended system behavior. Patches or mitigations should be available from HCL; refer to the support article KB0132828 for remediation guidance.
Affected products
- HCL MyXalytics
Timeline
- 2026-09-07: disclosed