Skip to main content
VulnerabilityPublished

CVE-2025-52625: HCL AION · CWE-525

Affects HCL AIONSource CVE Database V5

0

Not known to be exploited · CVSS 3.7 Low.

Data as of 26 Oct 2026, 14:05 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

  1. Immediately review and update web server and application configurations to ensure SSL pages are served with cache-control headers that prevent caching (e.g., Cache-Control: no-store, no-cache, must-revalidate; Pragma: no-cache).
  2. Disable caching of SSL content at the browser level where possible, especially on shared or public devices.
  3. Implement endpoint security controls to restrict unauthorized access to devices and browser caches, including disk encryption and user session management.
  4. Educate users about the risks of using shared devices and the importance of logging out and clearing browser caches after sessions involving sensitive applications.
  5. Monitor for any updates or patches from HCL addressing this vulnerability and apply them promptly once available.
  6. Conduct regular security audits to verify that sensitive pages are not cached and that cache-control policies are enforced consistently across all environments.
  7. Consider network-level controls that prevent caching of SSL traffic by proxies or intermediary devices.
  8. In high-risk environments, consider deploying additional data loss prevention (DLP) solutions to detect and block unauthorized data exposure from cached content.

Description

A vulnerability  Cacheable SSL Page Found vulnerability has been identified in HCL AION.  Cached data may expose credentials, system identifiers, or internal file paths to attackers with access to the device or browser This issue affects AION: 2.0.

References

Community reviews

Loading reviews…