Cyber Resilience

CVE-2025-52659

Hcltech Aion 2.0.0

Published
19 January 2026
Modified
25 April 2026
Patch / advisory
CVSS Score v3.1 2.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L
EPSS Score 0.0016 5th percentile
Risk Priority 24 floored blend · peak EPSS

Summary

CVE-2025-52659 is a low-severity Use of Web Browser Cache Containing Sensitive Information (CWE-525) vulnerability in Hcltech Aion. Its CVSS base score is 2.8 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-52659 is a Cacheable HTTP Response vulnerability, classified under CWE-525, affecting HCL AION version 2. This flaw may result in the unintended storage of sensitive or dynamic content in caches, potentially enabling unauthorized access or information disclosure. The vulnerability received a CVSS v3.1 base score of 2.8 (AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L) and was published on 2026-01-19.

Exploitation requires local access, low attack complexity, low privileges, and user interaction. A local attacker with low-level privileges could trick a user into performing an action that triggers a cacheable HTTP response containing sensitive or dynamic content. While the description notes potential for unauthorized access or disclosure, the CVSS metrics indicate no confidentiality or integrity impact, with effects limited to low availability disruption.

Mitigation guidance is available in the HCL Software support knowledge base article at https://support.hcl-software.com/kb_view.do?sys_kb_id=4b92474633de7ad4159a05273e5c7b4b&searchTerm=kb0127995#.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

HCL AION version 2 is affected by a Cacheable HTTP Response vulnerability. This may lead to unintended storage of sensitive or dynamic content, potentially resulting in unauthorized access or information disclosure.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-52625Same product: Hcltech Aion
CVE-2025-52642Same product: Hcltech Aion
CVE-2025-52623Same product: Hcltech Aion
CVE-2025-52627Same product: Hcltech Aion
CVE-2025-52634Same product: Hcltech Aion
CVE-2025-52630Same product: Hcltech Aion
CVE-2025-52649Same product: Hcltech Aion
CVE-2025-52631Same product: Hcltech Aion
CVE-2025-52632Same product: Hcltech Aion
CVE-2025-52644Same product: Hcltech Aion

Affected Assets

hcltech
aion
2.0.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V14.2.5
  • V14.3.2

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-01 mostly match
prevents

Configuration baselines and enforcement directly require proper Cache-Control and related headers.

PR.PS-06 mostly match
prevents

Secure SDLC practices include defining and verifying appropriate web caching policies for sensitive content.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

degrades

Endpoint device configuration can enforce cache-clearing or no-cache policies for sensitive web content.

prevents

Application security requirements can explicitly require no-cache headers or cache-control directives for sensitive pages.

prevents

Secure coding standards can mandate proper cache-control headers and form-field handling to prevent sensitive data retention.

prevents

Configuration management can mandate secure browser cache settings across the estate.

none

Web filtering can block risky sites but does not directly govern browser caching of sensitive data.

References