HCL MyXalytics is affected by the use of vulnerable/outdated versions

published 2025-10-03 13 mo ago modified 2026-10-08 31 d ago also EUVD-2025-32449

cvss: 3.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 9%
public exploits: 0; none known

HCL MyXalytics is affected by the use of vulnerable/outdated versions which can expose the application to known security risks that could be exploited.

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 13 mo ago (2025-10-03)

Exploit prediction

0.19% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	3.5	CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N
NVD	3.1	4.8	CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

Affected products

HCL Software MyXalytics

Classification

Weakness

CWE-1104 Use of Unmaintained Third Party Components
CWE-1021 Improper Restriction of Rendered UI Layers or Frames

References

support.hcl-software.com /csm?id=kb_article&sysparm_article=KB0124411
vendor-advisory

Sources

CVE List CVE-2025-52658
NVD CVE-2025-52658

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary