Skip to main content
VulnerabilityPublished

CVE-2025-52642: HCL AION · CWE-538

Affects HCL AIONSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.3 Low.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
3.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/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-52642, organizations should implement the following specific measures: 1) Review and sanitize all application responses, error messages, and logs to ensure internal filesystem paths are not disclosed to users or unauthorized personnel. 2) Restrict local access to HCL AION systems to trusted users only, enforcing strict access controls and monitoring for suspicious activity. 3) Educate users about the risks of interacting with untrusted content that could trigger path disclosures. 4) Monitor vendor communications closely for patches or updates addressing this vulnerability and apply them promptly once available. 5) Implement application-layer filtering or web application firewalls (WAFs) to detect and block responses containing sensitive path information. 6) Conduct regular security assessments and code reviews focusing on error handling and information leakage. 7) Employ logging and alerting mechanisms to detect unusual access patterns that might indicate reconnaissance attempts. These targeted actions go beyond generic advice by focusing on controlling information exposure and limiting local access vectors specific to this vulnerability.

Description

HCL AION is affected by a vulnerability where internal filesystem paths may be exposed through application responses or system behaviour. Exposure of internal paths may reveal environment structure details which could potentially aid in further targeted attacks or information disclosure.

References

Community reviews

Loading reviews…