Skip to main content
VulnerabilityPublished

CVE-2025-52649: HCL AION · Information Exposure

Affects HCL AIONSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 1.8 Low.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
1.8Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% 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:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
HCLAIONAffected
  • =2.0
Fixed in–

AI-suggested

To mitigate CVE-2025-52649, organizations should implement the following specific measures: 1) Restrict local access to HCL AION systems to trusted, authorized personnel only, minimizing the risk of attackers gaining the required local privileges. 2) Enforce strict privilege management and least privilege principles to reduce the number of users with high-level access. 3) Monitor and audit user interactions on AION systems to detect any unusual or unauthorized activity that could indicate attempts to exploit predictable identifiers. 4) Engage with HCL support or security advisories to obtain patches or updates once available and apply them promptly. 5) Consider additional application-layer controls such as input validation and randomization techniques for identifiers if customization or configuration options exist. 6) Educate system administrators and users about the risks of predictable identifiers and the importance of secure access controls. These steps go beyond generic advice by focusing on access control, monitoring, and proactive engagement with the vendor.

Description

HCL AION is affected by a vulnerability where certain identifiers may be predictable in nature. Predictable identifiers may allow an attacker to infer or guess system-generated values, potentially leading to limited information disclosure or unintended access under specific conditions.

References

Community reviews

Loading reviews…