# CVE-2025-42979: Insecure Key & Secret Management vulnerability in SAP GUI for Windows

> Attackers with local registry access can recover RFC user credentials due to insecure obfuscation instead of secure encryption in SAP GUI for Windows.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2025
- **Updated:** 8 Jul 2025
- **Also known as:** GHSA-3px8-gf2c-qqrh

## What is CVE-2025-42979?

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

### Official description

The GuiXT application, which is integrated with SAP GUI for Windows, uses obfuscation algorithms instead of secure symmetric ciphers for storing the credentials of an RFC user on the client PC. This leads to a high impact on confidentiality because any attacker who gains access to the user hive of this user�s windows registry could recreate the original password. There is no impact on integrity or availability of the application

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

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


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

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

## Is CVE-2025-42979 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42979 is a medium-severity vulnerability in SAP_SE SAP GUI for Windows, published on 8 Jul 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-42979 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-42979/ (Markdown: https://insights.sbomify.com/CVE-2025-42979/index.md)
```

## Sources

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

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