CVE-2025-36082VulnerabilityPublished 15 Sep 2025

CVE-2025-36082: IBM OpenPages · Information Exposure Through Browser Caching

Affects IBM OpenPagesSource CVE Database V5

Not known to be exploited · CVSS 4.0 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.0Medium

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

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

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

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

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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Sep 2025
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 2026-10-26.

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 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
IBM OpenPages	Affected =9.0 =9.1	Fixed in–

AI-suggested

To mitigate CVE-2025-36082, European organizations should implement several targeted measures beyond generic advice: 1) Configure browsers used to access IBM OpenPages to disable caching of sensitive pages, using settings or extensions that enforce no-store or no-cache directives. 2) Implement strict HTTP cache-control headers on the OpenPages web server to prevent caching of sensitive content by browsers. 3) Enforce endpoint security policies that restrict shared use of workstations or virtual desktops, ensuring user sessions are isolated and local file access is controlled. 4) Regularly clear browser caches and temporary internet files on shared systems, ideally automated via scripts or endpoint management tools. 5) Educate users about the risks of shared systems and the importance of logging out and closing browsers after sessions. 6) Monitor IBM for patches or updates addressing this vulnerability and apply them promptly once available. 7) Consider deploying OpenPages in environments with enhanced session isolation, such as dedicated virtual machines or containers per user. These steps collectively reduce the risk of local information exposure through browser caching.

Description

IBM OpenPages 9.0 and 9.1 allows web page cache to be stored locally which can be read by another user on the system.

Impact

For European organizations using IBM OpenPages 9.0 or 9.1, this vulnerability poses a risk of local information leakage. Since OpenPages is a governance, risk, and compliance (GRC) platform, the data exposed could include sensitive regulatory compliance information, audit results, risk assessments, or internal policies. In environments where multiple users share workstations or virtual desktops, such as in large enterprises, consulting firms, or government agencies, unauthorized users could access cached data from previous sessions, potentially leading to data confidentiality breaches. This could undermine compliance with European data protection regulations such as GDPR, especially if personal or sensitive data is involved. While the vulnerability does not allow remote exploitation or system compromise, the exposure of sensitive information could facilitate insider threats or lateral movement within an organization. The impact is more pronounced in sectors with high regulatory scrutiny, including finance, healthcare, and public administration. However, organizations with strict endpoint security and user session isolation may mitigate the risk somewhat. The absence of known exploits reduces immediate risk but does not eliminate the need for proactive mitigation.

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

ibm.com/support/pages/node/7244777 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Sep 2025, 15:40 UTC

WeaknessesCWE-525

Technical details

References

Community reviews

Related threats