{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-59870 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-59870 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-59870 is a high-severity vulnerability in HCL Software MyXalytics, published on 16 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-59870 and fix it if it is affected.\n\nWhat it is: CVE-2025-59870 is a high-severity vulnerability in HCL Software MyXalytics, published on 16 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-59870 in the wild and no public exploit code.\n\nAffected product: HCL Software MyXalytics. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-59870/ (Markdown: https://insights.sbomify.com/CVE-2025-59870/index.md)","id":"CVE-2025-59870","markdown":"https://insights.sbomify.com/CVE-2025-59870/index.md","name":"CVE-2025-59870","record":{"aliases":["GHSA-gfgr-857q-jxp3"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"HCL MyXalytics","requires_auth":"none","summary":"Static JWT signing secret without rotation allows attackers to potentially forge tokens and bypass authentication in HCL MyXalytics.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"HCL","cpe":[{"product":"myxalytics","vendor":"hcltech"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-323","name":"Reusing a Nonce, Key Pair in Encryption"}],"description":"HCL MyXalytics  is affected by improper management of a static JWT signing secret in the web application, where the secret lacks rotation , introducing a security risk","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Weak cryptography in MyXalytics","id":"CVE-2025-59870","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"HCL ZIE for Web is affetced by an Unrestricted File Upload vulnerability,","id":"CVE-2025-59872"},"packages":[],"prev":{"headline":"HCL Traveler for Microsoft Outlook (HTMO) is susceptible to sensitive data exposure","id":"CVE-2025-59868"},"products":["MyXalytics"],"published":"2026-01-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-21","vendors":["HCL Software"]},"summary":"Static JWT signing secret without rotation allows attackers to potentially forge tokens and bypass authentication in HCL MyXalytics.","url":"https://insights.sbomify.com/CVE-2025-59870/"}