CVE-2025-42888VulnerabilityPublished 11 Nov 2025Updated 12 Nov 2025

CVE-2025-42888: SAP GUI for Windows · Cleartext Storage of Sensitive Information in Memory

Affects SAP GUI for WindowsSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.5Medium

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:H/UI:R/S:C/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: Required
Scope: Changed
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: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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 11 Nov 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-25.

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
SAP_SE SAP GUI for Windows	Affected =8.10	Fixed in–

AI-suggested

To mitigate CVE-2025-42888, European organizations should implement the following specific measures: 1) Restrict local administrative privileges on client PCs running SAP GUI to only trusted personnel, minimizing the number of users who can access process memory. 2) Enforce strict endpoint security controls, including application whitelisting and memory protection technologies, to prevent unauthorized memory inspection tools from running. 3) Monitor and audit privileged user activities on SAP client machines to detect suspicious access patterns or attempts to extract memory data. 4) Segregate SAP client usage environments, avoiding shared workstations where possible, to reduce insider threat risks. 5) Engage with SAP support channels to obtain patches or updates as soon as they become available and plan timely deployment. 6) Educate IT and security teams about the vulnerability’s nature and the importance of controlling local access. 7) Consider deploying endpoint detection and response (EDR) solutions capable of detecting anomalous memory access or credential dumping attempts. 8) Review and harden SAP GUI configuration settings to minimize exposure of sensitive data in memory if configurable options exist. These targeted actions go beyond generic advice by focusing on local privilege management, monitoring, and preparation for vendor patches.

Description

SAP GUI for Windows may allow a highly privileged user on the affected client PC to locally access sensitive information stored in process memory during runtime.This vulnerability has a high impact on confidentiality, with no impact on integrity and availability.

Impact

For European organizations, the primary impact of CVE-2025-42888 is the potential exposure of sensitive SAP data due to cleartext storage in memory accessible by highly privileged local users. This can lead to unauthorized disclosure of confidential business information, intellectual property, or personal data processed through SAP systems. Industries such as manufacturing, finance, energy, and public sector entities that heavily rely on SAP ERP solutions are at heightened risk. The vulnerability does not affect system integrity or availability, so operational disruption is unlikely; however, confidentiality breaches can result in regulatory penalties under GDPR and damage to corporate reputation. The requirement for local high-privilege access limits remote exploitation risk but elevates insider threat concerns and risks from compromised administrative accounts. European organizations with shared workstations or insufficient endpoint security controls may be particularly vulnerable. The absence of known exploits reduces immediate risk but does not preclude targeted attacks. Overall, the vulnerability necessitates prompt attention to prevent sensitive data leakage within SAP client environments.

CWE-316Cleartext Storage of Sensitive Information in Memory (opens in a new tab)
Variant weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product stores sensitive information in cleartext in memory.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Nov 2025, 04:47 UTC

WeaknessesCWE-316

Technical details

References

Community reviews

Related threats