CVE-2025-52644: HCL AION · CWE-778
Affects HCL AIONSource CVE Database V5
Not known to be exploited · CVSS 5.8 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 16 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| HCLAION | Affected
| Fixed in– |
AI-suggested
Organizations should implement compensating controls to enhance audit logging and monitoring until an official patch is available. This includes enabling all available logging features in HCL AION, integrating logs with centralized Security Information and Event Management (SIEM) systems for real-time analysis, and conducting regular audits of user activities. Restrict local access to trusted personnel only and enforce the principle of least privilege to reduce the risk of exploitation. Employ host-based intrusion detection systems (HIDS) to detect anomalous behavior that may not be logged by the application. Additionally, establish strict change management and user activity review processes to identify suspicious actions early. Once HCL releases a patch, prioritize timely deployment. Finally, maintain comprehensive incident response plans that account for scenarios where audit trails may be incomplete or missing.
Description
HCL AION is affected by a vulnerability where certain user actions are not adequately audited or logged. The absence of proper auditing mechanisms may reduce traceability of user activities and could potentially impact monitoring, accountability, or incident investigation processes.