# CVE-2025-42888: Information Disclosure vulnerability in SAP GUI for Windows

> A highly privileged local user can access sensitive information from SAP GUI for Windows process memory, compromising confidentiality.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Nov 2025
- **Updated:** 12 Nov 2025
- **Also known as:** GHSA-59p6-qq9j-xgjc

## What is CVE-2025-42888?

CVE-2025-42888 is a medium-severity vulnerability in SAP_SE SAP GUI for Windows, published on 11 Nov 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-316 (Cleartext Storage of Sensitive Information in Memory)

## Which versions are affected by CVE-2025-42888?


## How do I fix CVE-2025-42888?

No fix has been published for CVE-2025-42888 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-42888 being exploited?

There is no known exploitation of CVE-2025-42888 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-42888 and fix it if it is affected.

What it is: CVE-2025-42888 is a medium-severity vulnerability in SAP_SE SAP GUI for Windows, published on 11 Nov 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-42888 in the wild and no public exploit code.

Affected product: SAP_SE SAP GUI for Windows. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-42888/ (Markdown: https://insights.sbomify.com/CVE-2025-42888/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-42888
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-42888
- OSV: https://osv.dev/vulnerability/CVE-2025-42888

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-42888/
Summaries are generated and may contain mistakes; the official description above is the record.