# CVE-2026-24317: DLL Hijacking vulnerability in SAP GUI for Windows with active GuiXT

> An attacker can execute arbitrary code in a victim's context by placing a malicious DLL in a directory loaded by SAP GUI when GuiXT is enabled.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Mar 2026
- **Updated:** 11 Mar 2026
- **Also known as:** GHSA-fwc5-f9r2-52h9

## What is CVE-2026-24317?

CVE-2026-24317 is a medium-severity vulnerability in SAP_SE SAP GUI for Windows with active GuiXT, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

SAP GUI for Windows allows DLL files to be loaded from arbitrary directories within the application. An unauthenticated attacker could exploit this vulnerability by persuading a victim to place a malicious DLL within one of these directories. The malicious command is executed in the victim user's context provided GuiXT is enabled. This vulnerability has a low impact on confidentiality, integrity, and availability.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2026-24317?


## How do I fix CVE-2026-24317?

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

## Is CVE-2026-24317 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24317 and fix it if it is affected.

What it is: CVE-2026-24317 is a medium-severity vulnerability in SAP_SE SAP GUI for Windows with active GuiXT, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-24317 in the wild and no public exploit code.

Affected product: SAP_SE SAP GUI for Windows with active GuiXT. 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-2026-24317/ (Markdown: https://insights.sbomify.com/CVE-2026-24317/index.md)
```

## Sources

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

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