Skip to main content
VulnerabilityPublished

CVE-2025-52631: 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, 10:12 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:L/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

European organizations should immediately verify that HCL AION 2.0 deployments enforce HTTPS connections and implement HSTS headers with appropriate parameters (e.g., 'max-age', 'includeSubDomains', and 'preload'). Network administrators should configure web servers or reverse proxies to add or correct the HSTS header if missing or misconfigured. Additionally, organizations should conduct security assessments to identify any insecure HTTP endpoints and redirect all HTTP traffic to HTTPS. Employing network-level protections such as TLS inspection, intrusion detection systems, and strict transport security policies can further reduce risk. User education to recognize and avoid insecure connections and suspicious prompts is also beneficial. Monitoring network traffic for downgrade attempts and anomalous behavior can help detect exploitation attempts. Finally, organizations should engage with HCL support for updates or patches and consider upgrading to newer versions if available.

Description

HCL AION is affected by a Missing or Insecure HTTP Strict-Transport-Security (HSTS) Header vulnerability. This can allow insecure connections, potentially exposing the application to man-in-the-middle and protocol downgrade attacks.. This issue affects AION: 2.0.

References

Community reviews

Loading reviews…