HCL AION CVE-2025-52634
HIGHAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify exposed HCL AION 2.0 endpoint
-
ExploitSend crafted unauthenticated request
-
ExecutionServer returns sensitive information
-
ImpactHarvest disclosed data for follow-on use
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The vulnerability affects HCL AION version 2.0 (CPE 2.0.0) and, per the CVSS vector (AV:N/AC:L/PR:N/UI:N), requires only network reachability to the AION instance - no authentication, no user interaction, and no special configuration are indicated by the available data. The primary limiting factors are therefore deployment-based rather than technical: the AION instance must be network-reachable by the attacker (exposure is far lower for instances restricted to internal networks or behind access controls), and only version 2.0 is listed as affected. The NVD description does not specify a required feature, protocol, or non-default setting, so no feature-gated precondition can be confirmed from the provided data; the exact exposure mechanism should be verified against HCL advisory KB0124444. |
| Impact | The CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/C:H/I:N/A:N) indicates a network-reachable, low-complexity, unauthenticated information-disclosure flaw with high confidentiality impact and no integrity or availability impact - consistent with the CWE-200 classification. However, exploitation-likelihood signals strongly temper this severity: the EPSS score is only 0.03% (9th percentile), the CVE is NOT listed in CISA KEV, and no public exploit code was identified in the provided intelligence. The sole reference is the HCL vendor advisory (KB0124444), and no SSVC decision data, POC, or active-exploitation evidence was supplied. These signals are consistent rather than conflicting: a genuinely unauthenticated remote data-exposure bug, but with no evidence of real-world exploitation and a product (HCL AION) that has a small deployment footprint. Net assessment: this is a legitimate high-severity confidentiality issue that AION operators should patch, but it is not a widespread exploitation priority - treat it as important-for-affected-deployments rather than an emergency across the broader estate. Key limitation: the NVD description is extremely sparse ('Exposure of Sensitive Information'), giving no detail on WHICH data is exposed or via what mechanism, so the real impact depends on vendor specifics - verify against HCL advisory KB0124444. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker sends requests to an internet-reachable HCL AION 2.0 instance and retrieves sensitive information that should not be accessible without authorization. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, no credentials, user interaction, or special timing are needed, making the request trivial to repeat. No public proof-of-concept exploit was identified at the time of analysis, so the exact disclosed data and endpoint must be confirmed from the HCL advisory. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 08, 2026
HCL AION 2.0 allows unauthenticated remote attackers to access sensitive information due to a CWE-200 information disclosure vulnerability (CVSS 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). This flaw requires only network reachability to the AION instance and has high confidentiality impact with no integrity or availability impact. No public exploit code or active exploitation has been identified at time of analysis, and EPSS is low at 0.03% (9th percentile).
Earlier versions of this analysis (1)
Information disclosure in HCL AION 2.0 allows unauthenticated remote attackers to access sensitive information via a high-complexity attack. No active exploitation or public exploit code has been identified, and EPSS score is very low (0.03%). The vulnerability affects only version 2.0.
RemediationAI
HCL has published advisory KB0124444 (https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0124444), which should be reviewed for specific remediation guidance, including any available software updates. At time of analysis, no exact fix version was provided in the available data. If a patch is not immediately available, restrict network access to AION 2.0 instances to trusted networks only, as the vulnerability is network-exploitable without authentication (AV:N/PR:N). This can be implemented via firewall rules, VPN requirements, or network segmentation; note that these measures may limit legitimate remote access. Additionally, monitor application logs for unauthorized information access attempts. The advisory may recommend further mitigations such as configuration changes.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CVE-2025-52634 is classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), a broad category covering flaws that leak sensitive data through various means such as error messages, directory listings, or improper access controls. The affected product is HCL AION version 2.0 (CPE: cpe:2.3:a:hcltech:aion:2.0.0). The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) indicates the vulnerability is remotely exploitable over the network with low complexity, requiring no authentication (PR:N) and no user interaction (UI:N). The confidentiality impact is high, while integrity and availability impacts are none, consistent with an information disclosure issue. The exact technical mechanism-whether it involves an API endpoint, improper access control, or data leakage in responses-is not specified in the available data and should be verified against HCL advisory KB0124444. The independent assessment notes that exposure is primarily deployment-based, as the instance must be network-reachable.
Know when Aion gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CWE-200 unauthenticated remote information disclosure warrants AV:N/AC:L/PR:N/UI:N with C:H and no integrity or availability impact, matching the vendor-assigned vector.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionNVD
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in HCL AION This issue affects HCL AION: 2.0.
Executive ViewAI
HCL AION 2.0 contains a high-severity information disclosure flaw that allows any unauthenticated party with network access to the AION instance to read sensitive data, with no credentials or user interaction required. Because exploitation leaves no integrity or availability footprint and the product is not patched, affected data could be exfiltrated without triggering typical disruption-based detection. Leadership should treat this as a data-confidentiality exposure affecting any business unit or partner whose information is processed through AION, and should note that regulatory notification obligations may arise if sensitive data is confirmed accessed.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict network reachability to HCL AION 2.0 instances via firewall rules, VPN-only or IP allow-listing; front the service with an authenticating reverse proxy or WAF that enforces authentication and request filtering; disable or restrict non-essential endpoints and services; enable and monitor access logging for unexpected requests to sensitive data paths; and isolate affected instances in a segmented network zone. Seek vendor guidance from HCL for a hotfix or configuration workaround.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Affected Products (CPE)NVD
HCL AION 2.0's Content Security Policy does not enforce Trusted Types for scripts, leaving a browser-level defense-in-de
HCL AION 2.0.0 can leak credentials, system identifiers, and internal file paths through cached HTTPS responses because
Information disclosure in HCL AION 2.0 allows unauthenticated, remote attackers to read sensitive data without user inte
Session cookies issued by HCL AION 2.0 are set without the Secure attribute (CWE-614), so a network-positioned attacker
Content security policy bypass in HCL AION v2.0 enables inline script injection, allowing remote attackers to modify web
Script allowlist bypass in HCL AION 2.0 allows unauthorized script execution through a misconfigured Content-Security-Po
HCL AION contains inadequate auditing and logging mechanisms that fail to properly track certain user actions, reducing
Insufficient anti-automation controls on certain HCL AION v2.1.0 endpoints allow scripted or automated requests to bypas
HCL AION contains a container base image authentication vulnerability where container images are not properly verified b
Aion versions up to 2.0 is affected by incorrect permission assignment for critical resource (CVSS 5.5).
HCL AION lacks adequate brute-force protections on authentication mechanisms, allowing repeated login attempts that coul
HCL AION fails to enforce encryption for certain data transmissions or operations, potentially exposing sensitive inform
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB