CVE-2025-55252: HCL Software AION · Weak Password Requirements
Affects HCL Software AIONSource CVE Database V5
Not known to be exploited · CVSS 3.1 Low.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:NExploitation 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| HCL SoftwareAION | Affected
| Fixed in– |
AI-suggested
European organizations using HCL AION version 2 should implement the following specific mitigations: 1) Enforce strong password policies externally if the product's native enforcement is weak, including minimum length, complexity, and expiration requirements. 2) Integrate multi-factor authentication (MFA) where possible to reduce reliance on passwords alone. 3) Conduct regular audits of user accounts to identify and remediate weak or default passwords. 4) Monitor authentication logs for unusual access patterns indicative of brute-force or guessing attempts. 5) Apply network segmentation and least privilege principles to limit the impact of compromised accounts. 6) Engage with HCL Software for updates or patches addressing this vulnerability and plan timely deployment once available. 7) Provide user training to raise awareness about secure password practices. These steps go beyond generic advice by focusing on compensating controls and proactive monitoring tailored to the specific weakness in AION's password policy enforcement.
Description
HCL AION version 2 is affected by a Weak Password Policy vulnerability. This can allow the use of easily guessable passwords, potentially resulting in unauthorized access