Unauthorized access via guessable passwords
Published Jan 19, 2026 · Updated Jan 19, 2026
Weak password requirements in HCL AION 2 allow attackers to gain unauthorized access by guessing permitted low-strength passwords. HCL has not published the affected password-validation locus or the specific rules that fail to reject low-strength passwords. HCL's assessment requires network access, high privileges, and user interaction, and bounds the impact to limited data disclosure and modification.
Summary
What happened
Weak password requirements in HCL AION 2 allow attackers to gain unauthorized access by guessing permitted low-strength passwords. HCL has not published the affected password-validation locus or the specific rules that fail to reject low-strength passwords. HCL's assessment requires network access, high privileges, and user interaction, and bounds the impact to limited data disclosure and modification.
The record
- CVE
- CVE-2025-55252
- Published
- Jan 19, 2026
- Updated
- Jan 19, 2026
- Vendor
- HCL Software
- Product
- HCL AION
- Classifications
- CWE-521, T1110
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jan 19, 2026CVE publishedPublication date reported by the CVE source.
- Jan 19, 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=2
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.
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