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

> An attacker with administrative privileges or user directory access can read sensitive user input data stored locally by SAP GUI for Windows.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 14 Jan 2025
- **Updated:** 14 Jan 2025
- **Also known as:** GHSA-mqx7-r2mm-q7pp

## What is CVE-2025-0055?

CVE-2025-0055 is a medium-severity vulnerability in SAP_SE SAP GUI for Windows, published on 14 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SAP GUI for Windows stores user input on the client PC to improve usability. Under very specific circumstances an attacker with administrative privileges or access to the victim�s user directory on the Operating System level would be able to read this data. Depending on the user input provided in transactions, the disclosed data could range from non-critical data to highly sensitive data, causing high impact on confidentiality of the application.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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


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

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

## Is CVE-2025-0055 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0055 is a medium-severity vulnerability in SAP_SE SAP GUI for Windows, published on 14 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0055 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-0055/ (Markdown: https://insights.sbomify.com/CVE-2025-0055/index.md)
```

## Sources

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

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