Skip to main content
VulnerabilityPublished Updated

CVE-2025-52630: HCL AION · Information Exposure

Affects HCL AIONSource CVE Database V5

0

Not known to be exploited · CVSS 3.7 Low.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
3.7Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
HCL AIONAffected
  • =2.0
Fixed in–

AI-suggested

European organizations should implement network segmentation and restrict access to HCL AION 2.0 instances to trusted internal networks only, minimizing exposure to external attackers. Monitoring and logging access to AION services can help detect anomalous or unauthorized attempts to retrieve sensitive information. Employing strict access control policies and validating API endpoints or interfaces for information leakage is critical. Organizations should engage with HCL support to obtain timelines for patches or updates addressing this vulnerability and apply them promptly once available. Additionally, conducting regular security assessments and penetration testing focused on information disclosure can identify potential exploitation paths. Where possible, sensitive data within AION should be encrypted or masked to reduce the impact of any exposure. Finally, staff awareness and incident response plans should include scenarios involving data exposure vulnerabilities.

Description

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in HCL AION.This issue affects AION: 2.0.

References

Community reviews

Loading reviews…