SAProuter is a widely deployed SAP component; unauthenticated RCE against it can lead to broad enterprise compromise and warrants org‑wide attention.
CVE-2026-0487
Unauthenticated DLL-load in SAProuter on Windows allows arbitrary code execution.
Is CVE-2026-0487 being exploited?
Not confirmed. CVE-2026-0487 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.21% probability of exploitation in the next 30 days.
How severe is CVE-2026-0487?
CVE-2026-0487 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-0487?
Not known from our data. No patch reference has been recorded for CVE-2026-0487, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-0487 affect?
CVE-2026-0487 affects SAProuter on Microsoft Windows, SAP NetWeaver environments using SAProuter. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-0487?
Restrict SAProuter access, run with least privilege, harden DLL search paths; apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated DLL search-order hijack enables remote arbitrary code execution, enabling full system compromise under the service account.
Immediate action required
- affectedKRNL64NUC 7.22
- affected7.22EXT
- affectedKRNL64UC 7.22
- affected7.53
- affectedSAP_ROUTER 7.53
- affected7.54
- affectedKERNEL 7.22
- affected7.77
- affected7.89
- affected7.93
- affected9.16
- affected9.17
- affected9.18
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.