CVE-2025-55250: HCL Software AION · Generation of Error Message Containing Sensitive Information
Affects HCL Software AIONSource CVE Database V5
Not known to be exploited · CVSS 1.8 Low.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 19 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| HCL SoftwareAION | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-55250, European organizations should implement the following specific measures: 1) Review and harden error handling configurations in HCL AION version 2 to ensure error messages do not expose sensitive technical details; customize error messages to be generic and avoid revealing internal system information. 2) Restrict local access to systems running AION to trusted administrators only, enforcing the principle of least privilege and using strong authentication mechanisms. 3) Monitor and audit logs for unusual error message patterns or unauthorized access attempts that could indicate exploitation attempts. 4) Implement network segmentation and access controls to limit the ability of attackers to gain local access or interact with the system. 6) Conduct security awareness training for privileged users to reduce the risk of social engineering or accidental triggering of error conditions. These targeted actions go beyond generic advice by focusing on error message management and access control specific to the affected product and vulnerability.
Description
HCL AION version 2 is affected by a Technical Error Disclosure vulnerability. This can expose sensitive technical details, potentially resulting in information disclosure or aiding further attacks.