VulnerabilityPublished 3 Feb 2026

CVE-2025-52628: HCL AION · CWE-1275

Affects HCL AIONSource CVE Database V5

Not known to be exploited · CVSS 4.6 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

4.6Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L

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

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: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: None: There is no loss of confidentiality within the impacted component.
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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Feb 2026
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
HCLAION	Affected =2.0	Fixed in–

AI-suggested

To mitigate CVE-2025-52628, organizations should first verify if they are running HCL AION version 2.0 and assess cookie configurations. Immediate steps include configuring cookies with the SameSite attribute set to 'Strict' or at minimum 'Lax' to prevent cookies from being sent in cross-site contexts. Implementing robust anti-CSRF tokens in all state-changing requests is essential to prevent unauthorized actions. Review and harden session management policies, ensuring cookies are marked Secure and HttpOnly to reduce exposure. Monitor web traffic for anomalous cross-site requests that could indicate exploitation attempts. Engage with HCL support or vendor channels to obtain patches or updates addressing this vulnerability. Additionally, conduct security awareness training to reduce risks from social engineering that could facilitate user interaction required for exploitation. Regularly audit web application security controls and perform penetration testing focused on CSRF and cookie handling. Employ web application firewalls (WAFs) with rules to detect and block CSRF attempts targeting HCL AION endpoints.

Description

HCL AION is affected by a Cookie with Insecure, Improper, or Missing SameSite vulnerability. This can allow cookies to be sent in cross-site requests, potentially increasing exposure to cross-site request forgery and related security risks. This issue affects AION: 2.0.

Impact

For European organizations, this vulnerability poses a moderate risk primarily to web applications and services using HCL AION 2.0 for business-critical processes. Successful exploitation could allow attackers to perform unauthorized actions on behalf of legitimate users, potentially leading to data integrity issues, unauthorized transactions, or service disruptions. While confidentiality is not directly impacted, the integrity and availability concerns could affect trust and operational continuity. Sectors such as finance, government, and healthcare, which often deploy enterprise middleware like HCL AION, may face increased risks if attackers leverage CSRF to manipulate workflows or disrupt services. The requirement for user interaction and low privilege reduces the likelihood of widespread automated exploitation but does not eliminate targeted attacks. The absence of known exploits in the wild currently limits immediate risk but does not preclude future exploitation. European organizations must consider the regulatory implications of such vulnerabilities, especially under GDPR, where service integrity and availability are critical.

CWE-1275Sensitive Cookie with Improper SameSite Attribute (opens in a new tab)
Variant weaknessLikelihood of exploit: MediumOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The SameSite attribute for sensitive cookies is not set, or an insecure value is used.
Implementation
Set the SameSite attribute of a sensitive cookie to 'Lax' or 'Strict'. This instructs the browser to apply this cookie only to same-domain requests, which provides a good Defense in Depth against CSRF attacks.
OWASP Cheat Sheets
Cross-Site Request Forgery Prevention (opens in a new tab)
Session Management (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V3.4.3 (opens in a new tab)
V1.14.1 (opens in a new tab)
V1.4.4 (opens in a new tab)
Attack patterns
Cross Site Request Forgery (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=KB0127972 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Feb 2026, 18:48 UTC

WeaknessesCWE-1275

Technical details

References

Community reviews

Related threats