HCL AION 2.0 permission assignment

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.6$0-$5k0.00

Summaryinfo

A vulnerability has been found in HCL AION 2.0 and classified as problematic. Affected by this issue is some unknown functionality. The manipulation leads to permission assignment. This vulnerability is documented as CVE-2025-52627. It is possible to launch the attack on the physical device. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in HCL AION 2.0. This issue affects an unknown part. The manipulation with an unknown input leads to a permission assignment vulnerability. Using CWE to declare the problem leads to CWE-732. The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Root File System Not Mounted as Read-Only configuration vulnerability. This can allow unintended modifications to critical system files, potentially increasing the risk of system compromise or unauthorized changes.This issue affects AION: 2.0.

The advisory is shared at support.hcl-software.com. The identification of this vulnerability is CVE-2025-52627 since 06/18/2025. The exploitation is known to be difficult. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.6
VulDB Meta Temp Score: 5.6

VulDB Base Score: 3.8
VulDB Temp Score: 3.7
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔒

CNA Base Score: 5.5
CNA Vector (HCL): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Permission assignment
CWE: CWE-732 / CWE-275 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒

Physical: Yes
Local: Yes
Remote: Yes

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

06/18/2025 CVE reserved
02/03/2026 +230 days Advisory disclosed
02/03/2026 +0 days VulDB entry created
02/11/2026 +8 days VulDB entry last update

Sourcesinfo

Advisory: KB0127972
Status: Not defined

CVE: CVE-2025-52627 (🔒)
GCVE (CVE): GCVE-0-2025-52627
GCVE (VulDB): GCVE-100-344081

Entryinfo

Created: 02/03/2026 21:09
Updated: 02/11/2026 04:44
Changes: 02/03/2026 21:09 (61), 02/11/2026 04:44 (11)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!