LiveActive security incident?Get immediate response
CVE Record

CVE-2025-52640: HCL AION is affected by multiple security vulnerabilities.

HCL AION is affected by a vulnerability where the shared storage used by product components is architected without sufficient access separation. Processes sharing the storage may be able to access or modify files beyond their intended scope, potentially resulting in unintended behavior or security impact under certain conditions.

MediumCVSS 4.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

HCL AION v2.0 uses shared storage without sufficient separation between product components. A process may access or alter files outside its intended scope, potentially affecting confidentiality, integrity, or availability. Exploitation is constrained by local access, high privileges, high complexity, and required user interaction.

Executive priority

Treat this as a planned remediation priority, with faster action on sensitive or multi-user systems. The moderate score and demanding prerequisites reduce urgency, but privileged cross-component file modification could undermine application trust.

Technical view

CVE-2025-52640 is a CWE-276 access-control weakness in HCL AION v2.0 shared storage. Its CVSS 3.1 score is 4.7: local attack vector, high complexity, high privileges, user interaction, changed scope, and low impact across confidentiality, integrity, and availability.

Likely exposure

Exposure is limited to identified HCL AION v2.0 deployments where product processes share storage. The supplied record lists other versions as unaffected by default, but provides no deployment-specific configuration details.

Exploitation context

The supplied sources do not report active exploitation, and the CVE is not listed as KEV in the bundle. The CVSS assessment indicates exploitation requires local access, high privileges, high complexity, and user interaction.

Researcher notes

The public bundle identifies the architectural weakness and CVSS assessment but does not provide affected configurations, patch versions, or vendor mitigation details. Testing should remain authorized and focus on access boundaries between component identities without developing weaponized procedures.

Mitigation direction

  • Inventory HCL AION installations and identify systems running v2.0.
  • Review the HCL advisory for vendor-approved remediation or updated-version guidance.
  • Restrict shared-storage permissions to only the component identities that require access.
  • Reduce unnecessary local privileged access while remediation is evaluated.

Validation and detection

  • Confirm installed AION versions using authoritative asset or package records.
  • Review shared-storage ownership, permissions, and access-control assignments.
  • Verify each product component cannot access files outside its intended scope.
  • Monitor shared storage for unexpected file access or modification activity.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-276: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-52640 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.7CVSS 3.1MediumCVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:L0.63.7HCL

Vulnerability scoring details

Base CVSS 3.1 score

4.7Medium
CVSS 3.1 vector shape for CVE-2025-52640Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HCL SoftwareAIONv2.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-276 · source CWE mapping

Incorrect Default Permissions

Incorrect Default Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.