VulnerabilityPublished 19 Jan 2026Updated 20 Jan 2026

CVE-2025-52659: HCL Software AION · Use of Web Browser Cache Containing Sensitive Information

Affects HCL Software AIONSource CVE Database V5

Not known to be exploited · CVSS 2.8 Low.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

2.8Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
HCL SoftwareAION	Affected =2	Fixed in–

AI-suggested

To mitigate CVE-2025-52659, organizations should implement the following specific measures: 1) Review and update HTTP response headers in HCL AION applications to include Cache-Control directives such as 'no-store', 'no-cache', and 'private' for any sensitive or dynamic content to prevent caching by browsers. 2) Employ the 'Pragma: no-cache' and 'Expires: 0' headers as additional safeguards for legacy clients. 3) Conduct a thorough audit of all web application endpoints to identify any responses that may inadvertently include sensitive data and ensure they are properly marked as non-cacheable. 4) Educate users about the risks of using shared or public devices and encourage secure browsing habits, including clearing browser caches regularly. 5) Implement endpoint security controls to restrict unauthorized local access to user devices, such as disk encryption and strong authentication mechanisms. 6) Monitor application logs and user activity for unusual access patterns that may indicate attempts to exploit cached data. 7) Stay informed about vendor updates and apply patches promptly once available. 8) Consider deploying web application firewalls (WAFs) that can enforce cache-control policies at the network edge. These targeted actions go beyond generic advice by focusing on HTTP header management, user education, and endpoint security tailored to the nature of this vulnerability.

Description

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.

Impact

For European organizations, the impact of CVE-2025-52659 is generally low but context-dependent. If sensitive or dynamic content is cached improperly, unauthorized users with access to the affected user's device could retrieve sensitive information, leading to potential data leakage. This risk is heightened in shared or public workstations, or in environments with weak endpoint security controls. The vulnerability does not directly compromise system confidentiality or integrity over the network, but it can facilitate local information disclosure. Availability impact is minimal, mostly related to potential stale or corrupted cache data affecting application behavior. Organizations handling sensitive personal data under GDPR must consider the risk of inadvertent data exposure through browser caches, which could lead to compliance issues and reputational damage. The lack of known exploits and the requirement for local access reduce the immediate threat level, but the vulnerability should be addressed proactively to maintain secure data handling practices.

CWE-525Use of Web Browser Cache Containing Sensitive Information (opens in a new tab)
Variant weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The web application does not use an appropriate caching policy that specifies the extent to which each web page and associated form fields should be cached.
Architecture and Design
Protect information stored in cache.
Implementation
Use a restrictive caching policy for forms and web pages that potentially contain sensitive information, such as "no-cache" in the Cache-Control header.
Architecture and Design
Do not store unnecessarily sensitive information in the cache.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V8.2.1 (opens in a new tab)
V8.1.1 (opens in a new tab)
V8.1.2 (opens in a new tab)
Attack patterns
Retrieve Embedded Sensitive Data (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.hcl-software.com/kb_view.do?sys_kb_id=4b92474633de7ad4159a05273e5c7b4b&searchTerm=kb0127995 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Jan 2026, 19:53 UTC

WeaknessesCWE-525

Technical details

References

Community reviews

Related threats