External risk intelligence

HCL AION 2.0 Trusted Types Bypass Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2025-52635

HCL AION is an AI-driven automation and orchestration platform designed for enterprise environments. Such platforms are typically deployed as centralized web-based services, management portals, or API-driven hubs to facilitate automation workflows across the organization, making it likely they are reachable via internal or external network segments.

Hcltech Aion

2.0.0

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability has been found in HCL AION that could allow unauthorized access and modification of data. This issue stems from how trusted types in scripts are handled and not fully enforced by the Content Security Policy.

Script type enforcement weakness found.
It affects a core automation platform.
Assess relevance to confirm exposure.

Attack Path

How an attacker could exploit the issue

An attacker could potentially reach an HCL AION system over the network without needing any prior authentication or privileges. If the system is configured with a Content Security Policy that doesn't properly validate trusted types within scripts, an attacker might be able to trigger this vulnerability, potentially leading to a compromise of confidentiality, integrity, and availability.

No prior authentication or privileges required.
Exploits untrusted types in scripts.
Leads to full system compromise.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to impact the integrity and availability of the HCL AION system. Specifically, it might enable the execution of arbitrary code or script due to a failure in enforcing trusted types within Content Security Policy (CSP) directives. This could lead to unauthorized modifications or disruptions of the service's normal operation.

System integrity and availability.
Trusted types in scripts not enforced.
Potential for arbitrary code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-world ownership of this vulnerability likely falls to the platform or application owners responsible for HCL AION, in coordination with infrastructure and security teams. The immediate priority is to locate all instances of HCL AION, assess their network exposure and business criticality, and identify the accountable system owners to formulate a targeted remediation plan.

Platform or Application Owners
Verify HCL AION instance exposure and criticality.
Plan and coordinate remediation actions.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is HCL AION?

HCL AION is an enterprise-grade platform used for AI-driven automation and orchestration. Organizations rely on it as a centralized hub or management portal to coordinate and manage complex workflows across their digital infrastructure. Because it acts as a critical backend for automated processes, it is typically hosted as a web-based service or API-driven application.

What does CVE-2025-52635 mean for HCL AION?

This vulnerability is classified as CWE-1032, which involves a failure to properly enforce Trusted Types within a Content Security Policy (CSP). In plain terms, the application fails to verify that scripts being executed are trusted and safe. This weakness allows an attacker to bypass security controls meant to prevent unauthorized or malicious code from running within the application environment.

How can an attacker trigger this vulnerability?

An attacker can trigger this issue by sending malicious network traffic to the HCL AION system. The vulnerability does not require any prior authentication, user interaction, or special privileges to initiate. Simply interacting with the application via the network is sufficient; standard administrative actions or internal system usage are not required to create the conditions for this weakness.

Is my HCL AION instance at risk?

Halo Surface Signal indicates that HCL AION is often deployed as a web-based service reachable across network segments. If your instance is accessible via the network—whether internally or externally—it is potentially reachable by an attacker. You should evaluate your network configuration to determine if the instance is exposed to segments where untrusted traffic may originate.

When should I take action for this vulnerability?

You should begin by locating all active HCL AION instances and identifying the teams responsible for them. Prioritize these systems based on their business criticality and current network exposure. Your immediate goal is to verify if your deployments are affected and coordinate with your infrastructure teams to establish a formal remediation plan as soon as possible.

References

support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0124444

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.