CVE-2025-52631
Published: 03 February 2026
Summary
CVE-2025-52631 is a low-severity Exposure of Sensitive Information to an Unauthorized Actor (CWE-200) vulnerability in Hcltech Aion. Its CVSS base score is 3.7 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Adversary-in-the-Middle (T1557); ranked at the 9.8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified are NIST 800-53 SC-8 (Transmission Confidentiality and Integrity) and CM-6 (Configuration Settings).
Deeper analysis
CVE-2025-52631, published on 2026-02-03, is a Missing or Insecure HTTP Strict-Transport-Security (HSTS) Header vulnerability affecting HCL AION version 2.0. Mapped to CWE-200, it has a CVSS v3.1 base score of 3.7 (AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:L). The flaw enables insecure connections, potentially exposing the application to man-in-the-middle attacks and protocol downgrades.
Exploitation is possible over the network by an attacker with low privileges who must overcome high attack complexity and rely on user interaction. Successful attacks can achieve low-impact effects on confidentiality and availability, with no integrity impact.
Mitigation details are available in the HCL support advisory at https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0127972.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-206680
Vulnerability details
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Missing HSTS directly enables Adversary-in-the-Middle attacks via connection interception and protocol downgrade on web traffic.
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Directly requires cryptographic protection of transmitted information to enforce confidentiality/integrity and block downgrade/MITM attacks that the missing HSTS header enables.
Boundary-protection mechanisms (e.g., proxies or gateways) can be configured to insert or enforce HSTS headers on all HTTP responses for the affected AION application.
Requires secure configuration settings that would mandate the presence and correct values of security-related HTTP response headers such as Strict-Transport-Security.