Unauthenticated impersonation via static JWT signing secret
Published Jan 16, 2026 · Updated Jan 16, 2026
Authentication-token forgery in HCL Software MyXalytics 6.2 through 6.7 allows remote attackers to impersonate users via crafted JWTs. The web application reuses a static JWT signing secret without rotation, allowing anyone who learns the secret to sign tokens that its JWT validation accepts. Network access and knowledge of the secret are required; accepted tokens can expose or alter application data without interrupting service.
Summary
What happened
Authentication-token forgery in HCL Software MyXalytics 6.2 through 6.7 allows remote attackers to impersonate users via crafted JWTs. The web application reuses a static JWT signing secret without rotation, allowing anyone who learns the secret to sign tokens that its JWT validation accepts. Network access and knowledge of the secret are required; accepted tokens can expose or alter application data without interrupting service.
The record
- CVE
- CVE-2025-59870
- Published
- Jan 16, 2026
- Updated
- Jan 16, 2026
- Vendor
- HCL Software
- Product
- MyXalytics
- Classifications
- CWE-323, T1606
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 16, 2026CVE publishedPublication date reported by the CVE source.
- Jan 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.2 <=6.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo