CVE-2025-52635VulnerabilityPublished 10 Oct 2025

CVE-2025-52635: HCL AION · CWE-1032

Affects HCL AIONSource CVE Database V5

Not known to be exploited · CVSS 3.7 Low.

Data as of 25 Oct 2026, 19:02 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 17% 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:L/I:N/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within 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 2026-10-25.

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 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 implement the following specific mitigations: 1) Monitor HCL's official channels for patches or updates addressing CVE-2025-52635 and apply them promptly once available. 2) Review and strengthen CSP configurations to enforce trusted types rigorously, potentially adding custom CSP directives that restrict script sources and types beyond default settings. 3) Conduct internal security testing focusing on CSP enforcement and trusted types to identify any exploitable weaknesses. 4) Employ runtime application self-protection (RASP) or web application firewalls (WAF) with rules designed to detect and block unauthorized script execution attempts. 5) Educate development and security teams about trusted types and CSP best practices to prevent similar issues in future deployments. 6) Limit exposure by restricting network access to HCL AION management interfaces and services to trusted internal networks or VPNs. These steps go beyond generic advice by focusing on CSP hardening and proactive monitoring specific to this vulnerability.

Description

A rusted types in scripts not enforced in CSP vulnerability has been identified in HCL AION.This issue affects AION: 2.0.

Impact

For European organizations, the primary impact of CVE-2025-52635 is a potential confidentiality risk due to the possibility of unauthorized script execution bypassing CSP protections. This could lead to limited exposure of sensitive information handled by HCL AION applications. However, the vulnerability does not affect data integrity or system availability, reducing the risk of service disruption or data tampering. The high attack complexity and lack of known exploits lower the immediate threat level. Nonetheless, organizations in sectors with strict data protection requirements, such as finance, healthcare, and government, should be cautious, as even limited confidentiality breaches can have regulatory and reputational consequences under GDPR and other frameworks. The impact is more pronounced for entities heavily reliant on HCL AION 2.0 for critical business processes or digital services.

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:46 UTC

WeaknessesCWE-1032

Technical details

References

Community reviews

Related threats