VulnerabilityPublished 10 Oct 2025

CVE-2025-52632: HCL AION · CWE-614

Affects HCL AIONSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% 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:H/I:L/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
HCL AION	Affected =2.0	Fixed in–

AI-suggested

European organizations should immediately review their HCL AION 2.0 deployments to verify cookie configurations. Specifically, ensure that all session cookies have the Secure attribute set to enforce transmission only over HTTPS. Additionally, implement HTTP Strict Transport Security (HSTS) headers to force browsers to use HTTPS connections exclusively. Network monitoring should be enhanced to detect unusual session activity or repeated failed authentication attempts indicative of session hijacking attempts. Where possible, upgrade to a patched version of HCL AION once available. In the interim, consider deploying web application firewalls (WAFs) with rules to block non-HTTPS cookie transmissions and conduct security awareness training to reduce risks from insecure network usage. Regular security audits and penetration testing should include checks for cookie attribute misconfigurations.

Description

A Missing Secure Attribute in Encrypted Session (SSL) Cookie vulnerability in HCL AION.This issue affects AION: 2.0.

Impact

For European organizations, the missing Secure attribute in session cookies can lead to interception of session tokens if users access services over unsecured networks or if attackers perform man-in-the-middle attacks on HTTP traffic. This compromises confidentiality by allowing attackers to hijack user sessions, potentially gaining unauthorized access to sensitive data or systems. The integrity and availability of systems are less affected. Organizations in sectors such as finance, healthcare, and government, which often use HCL AION for business process automation, could face data breaches or unauthorized access incidents. The medium severity rating suggests a moderate risk, but the impact could be significant if exploited in targeted attacks against critical infrastructure or sensitive applications. The lack of known exploits provides some time for mitigation, but proactive measures are essential to prevent exploitation.

CWE-614Sensitive Cookie in HTTPS Session Without 'Secure' Attribute (opens in a new tab)
Variant weaknessOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The Secure attribute for sensitive cookies in HTTPS sessions is not set.
Implementation
Always set the secure attribute when the cookie should be sent via HTTPS only.
OWASP Cheat Sheets
Cross-Site Request Forgery Prevention (opens in a new tab)
Session Management (opens in a new tab)
OWASP ASVS 4.0.3
V3.4.1 (opens in a new tab)
V8.3.1 (opens in a new tab)
V9.2.2 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0124444 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Oct 2025, 10:18 UTC

WeaknessesCWE-614

Technical details

References

Community reviews

Related threats