CVE-2026-0487
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.
NVD · uneditedSAProuter on Microsoft Windows allows an unauthenticated attacker to load library (DLL) files from an untrusted location, allowing them to execute malicious code on the system. This could enable the attacker to hijack the DLL loading process and achieve arbitrary code execution. This has high impact on confidentiality, integrity and availability of the system.
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.
dbcve analysis · moderate confidenceSAProuter on Microsoft Windows contains a DLL planting vulnerability where an unauthenticated attacker can load malicious library files from an untrusted location, allowing arbitrary code execution through DLL hijacking.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm SAProuter is installed on WindowsCheck for SAProuter process running: Open Task Manager and look for 'saprouter.exe' in the Processes tab, or run 'tasklist | findstr -i saprouter' in Command PromptAffected if SAProuter process is running on the Windows system
-
Locate SAProuter installation directorySearch for saprouter.exe using Windows Explorer search or run 'where /r C:\ saprouter.exe' in Command Prompt. Common paths include C:\saprouter\ or C:\usr\sap\. Default installation directories under C:\Program Files\SAP or C:\SAP may also existAffected if SAProuter executable is found on the system
-
Identify installed SAProuter versionRun 'saprouter.exe -v' or 'saprouter.exe -V' from the installation directory, or right-click saprouter.exe, select Properties, and check the Version tabAffected if Version cannot be determined or is older than vendor-patched version
-
Check DLL search order configurationInspect SAProuter configuration files (saprouter.conf, saprouttab) in the installation directory for any DLL search path settings or registry entries under HKLM\SOFTWARE\SAP\SAProuter for DLL-related parametersAffected if No secure DLL search order is configured, or configuration allows loading from current working directory
-
Audit DLL files in SAProuter directory and related pathsExamine the SAProuter installation folder and subdirectories for unauthorized or unexpected DLL files. Also check C:\Windows\System32 and the directory from which SAProuter is launched for suspicious DLLs that could be hijackedAffected if Unexpected DLL files are present in the SAProuter directory or in paths that precede system DLLs in the search order
If SAProuter is running on a Windows system where the DLL search order allows loading from untrusted directories, the system is vulnerable to DLL hijacking attacks.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply vendor security patches for SAProuter and ensure the application loads DLLs only from trusted, secure locations using absolute paths or secure DLL search order configurations.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0487 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0487 in production — separate from our analysis above.
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.
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.
- 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