Skip to main content
VulnerabilityPublished

CVE-2025-52633: HCL AION · CWE-539

Affects HCL AIONSource CVE Database V5

0

Not known to be exploited · CVSS 3.1 Low.

Data as of 26 Oct 2026, 15:59 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Feb 2026

  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
HCLAIONAffected
  • =2.0
Fixed in–

AI-suggested

To mitigate this vulnerability, organizations should: 1) Review and modify cookie management policies to avoid storing sensitive session information in persistent cookies; use session cookies with appropriate expiration instead. 2) Implement secure cookie attributes such as HttpOnly, Secure, and SameSite to reduce the risk of interception and cross-site attacks. 3) Employ encryption or tokenization for any sensitive data that must be stored client-side. 4) Conduct regular security assessments and penetration testing focused on session management and cookie handling. 5) Monitor network traffic for signs of cookie theft or session hijacking attempts. 6) Engage with HCL for official patches or updates addressing this issue. 7) Educate users about the risks of session hijacking and encourage safe browsing practices. 8) Consider implementing multi-factor authentication to reduce the impact of compromised session tokens. These steps go beyond generic advice by focusing on cookie-specific controls and organizational processes tailored to HCL AION deployments.

Description

HCL AION is affected by a Permanent Cookie Containing Sensitive Session Information vulnerability. It is storing sensitive session data in persistent cookies may increase the risk of unauthorized access if the cookies are intercepted or compromised. This issue affects AION: 2.0.

References

Community reviews

Loading reviews…