HCL MyXalytics is affected by multiple security vulnerabilities.

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps HCL Software/MyXalytics (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for HCL Software/MyXalytics.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 7, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 7, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 7, 2026

Sources and claim methodology

• Source referencesupport.hcl-software.com

Related CVEs

• HCL MyXalytics is affected by multiple security vulnerabilities.Same hcl software/myxalytics package
• HCL MyXalytics is affected by multiple security vulnerabilities.Same hcl software/myxalytics package
• nRF54H20: MCUBoot can be tricked to executing unauthenticated codeSame generic ecosystem
• The Continuous Glucose Monitoring Service's Record Access Control Point (RACP) write handler `memcpy`s the entire attacker-supplied ATT write value into a fixed 20-byte BSS buffer.Same generic ecosystem
• QSPI flash encryption side-channel leakageSame generic ecosystem
• Powerkit <= 3.0.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via Lazy Load Image ProcessingSame generic ecosystem