Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2026-24317

MEDIUM · 5.0 CVSS v3.1 Published 2026-03-10

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

57/100

Remediation priority · Elevated

Remotely reachable No privileges

Official description

NVD · unedited

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.

Technical summary

dbcve analysis · moderate confidence

SAP GUI for Windows with GuiXT enabled is vulnerable to DLL hijacking, allowing the application to load malicious DLL files from arbitrary directories within the application. An unauthenticated attacker must persuade a victim to place a malicious DLL in a directory from which SAP GUI loads DLLs, resulting in code execution in the victim's user context.

MitigationDisable GuiXT if not required, or implement strict directory access controls to prevent users from placing files in SAP GUI DLL load paths. Monitor for unauthorized DLL placement and educate users about the risks of placing files in application directories.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: High
Privileges: None
User interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify SAP GUI for Windows is installed

Check for SAP GUI installation directory (commonly C:\Program Files\SAP\ or C:\Program Files (x86)\SAP\) and confirm saplogon.exe or similar SAP GUI executables exist

Affected if SAP GUI for Windows is installed and running
Confirm GuiXT module is loaded

Look for GuiXT.dll in the SAP GUI installation directory, or check SAP GUI configuration files (e.g., sapguistart.ini) for GuiXTEnable=1 or similar entries, or observe if GuiXT appears in the SAP GUI title bar or menu when running the application

Affected if GuiXT is enabled and loaded by SAP GUI
Identify SAP GUI DLL load directories

Use Sysinternals Process Monitor or similar tool to monitor DLL search paths when SAP GUI starts, or check the PATH environment variable and SAP GUI installation bin directory for directories where DLLs are loaded from

Affected if SAP GUI loads DLLs from one or more directories that could be user-writable
Check DLL load path directories for write access

Review file system permissions on identified DLL load directories (typically the SAP GUI installation bin folder and directories listed in the system PATH used by SAP GUI) to determine if standard users can create or modify files in those locations

Affected if Any SAP GUI DLL load directory is writable by non-privileged users, allowing placement of malicious DLLs
Scan for suspicious DLLs in SAP GUI directories

Use antivirus or file integrity monitoring tools to scan the SAP GUI installation directory and DLL load paths for unknown or recently added DLL files that could be malicious

Affected if Unexpected or unrecognized DLL files exist in SAP GUI DLL load directories

A user is affected if SAP GUI for Windows with GuiXT enabled is installed on their system and any directory in SAP GUI's DLL search path is writable by users who could place malicious DLLs.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Disable GuiXT if not required, or implement strict directory access controls to prevent users from placing files in SAP GUI DLL load paths. Monitor for unauthorized DLL placement and educate users about the risks of placing files in application directories.

Have this fixed Scoped from the published advisory

Consultation4.0 h
Implementation4.0 h
Testing2.0 h
Review / QA2.0 h

12.0 hours of engineering $2,180

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,488.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-24317 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24317 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-24317?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 5.0 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Remediation

Need this fixed?

Have this fixed 12 hrs · Moderate

Typical engagement from $2,180

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-24317 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References