VulnerabilityPublished 3 Mar 2026Updated 4 Mar 2026

CVE-2025-36364: IBM DevOps Plan · Use of Web Browser Cache Containing Sensitive Information

Affects IBM DevOps PlanSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.2 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

6.2Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% 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:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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 3 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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
IBMDevOps Plan	Affected >=3.0.0 <=3.0.5	Fixed in–

CPE configurations (2)

cpe:2.3:a:ibm:devops_plan:3.0.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:devops_plan:3.0.5:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2025-36364, organizations should implement the following specific measures: 1) Upgrade IBM DevOps Plan to a version beyond 3.0.5 once a patch is released by IBM addressing the caching behavior. 2) Until a patch is available, configure browsers used to access IBM DevOps Plan to disable or limit caching, especially for sensitive sites, by enforcing cache-control headers or using private/incognito modes. 3) Enforce strict access controls on shared systems to prevent unauthorized local user access, including user account separation and session locking. 4) Use endpoint security solutions to monitor and restrict access to browser cache directories. 5) Educate users about the risks of shared systems and the importance of logging out and locking sessions. 6) Consider deploying IBM DevOps Plan in isolated environments or virtual machines dedicated per user to reduce shared cache exposure. 7) Regularly audit and monitor local system access logs to detect suspicious activity. These steps go beyond generic advice by focusing on browser cache management and local access controls tailored to this vulnerability's characteristics.

Description

IBM DevOps Plan 3.0.0 through 3.0.5 allows web page cache to be stored locally which can be read by another user on the system.

Impact

The primary impact of CVE-2025-36364 is the potential unauthorized disclosure of sensitive information stored in the IBM DevOps Plan web interface. This can lead to exposure of confidential project details, credentials, or operational data to unauthorized local users sharing the same system. While the vulnerability does not affect data integrity or system availability, the confidentiality breach could facilitate further attacks such as social engineering, insider threats, or lateral movement within an organization. Organizations with shared workstations, remote desktop environments, or multi-user systems are particularly vulnerable. The impact is limited to local attackers, so remote exploitation is not feasible without prior system access. However, in environments with lax physical or logical access controls, this vulnerability could significantly increase the risk of data leakage and compliance violations, especially in regulated industries using IBM DevOps Plan for critical development workflows.

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/7261930 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (2)

Description

AI analysisMachine-generated, updated 11 Mar 2026, 20:12 UTC

WeaknessesCWE-525

Technical details

References

Community reviews

Related threats