On this page (7 sections)
CVE-2026-89103 is a critical flaw in SAP Gateway, published in the National Vulnerability Database on 2026-11-10 with a CVSS score of 10. According to the record, SAP Gateway activates a default Access Control List (ACL) with high privileges, which allows an external attacker to be categorized as an internal application server.
If you run SAP systems, especially ones where the Gateway is reachable from more than a tightly controlled internal network, this one deserves attention. The public record is short, so this article separates what is confirmed from what you still need to confirm in SAP's own materials.
What happened
The NVD entry describes a weakness in the default access control of SAP Gateway. The default ACL is activated with high privileges, and that allows an external attacker to be categorized as an internal application server. The record says an unauthenticated attacker with network access to the Gateway could then potentially perform unauthorized actions within the application environment.
The record describes a high impact on the confidentiality, integrity and availability of the affected system, and lists a CVSS score of 10. It does not include a scoring vector or further rationale, so this article does not go beyond those stated figures.
Technical details in plain terms
The weakness is classified as CWE-863, incorrect authorization. In general terms, this class covers cases where software makes a wrong decision about what a party is allowed to do. How SAP Gateway implements its access checks is not described in the sources reviewed, so this article does not speculate about the internal mechanism.
What the NVD text does make clear is the precondition: the attacker is unauthenticated but needs network access to the SAP Gateway. That makes network placement and segmentation a real part of your risk, alongside patch status.
Who is affected
Anyone operating SAP Gateway should treat their systems as in scope until they confirm otherwise. The record does not list affected version ranges, so you cannot rule yourself out from the NVD text alone. Exposure is likely to be highest where:
- The Gateway ports are reachable from the internet, partner networks or flat internal networks with many untrusted hosts.
- Systems were deployed with default Gateway access settings and never reviewed.
- SAP landscapes are managed by a separate team from the one that owns firewalls, so exposure is not obvious to either side.
How to check your exposure
Start with the vendor material. The NVD record points to SAP Note 3798345 and the SAP Security Patch Day page. These are the places to confirm affected releases and the correction. Access to SAP Notes normally requires an SAP account.
- Inventory every SAP system in your landscape that runs SAP Gateway, including development and test systems.
- Open SAP Note 3798345 and compare the affected components and releases against your inventory.
- Check from the network side which Gateway ports are reachable, and from where. Use your own firewall rules and, for hosts you own, a check from outside your trusted network.
- Review how the Gateway's access control lists are configured on each system, and whether defaults are still in use.
What to do now
- Read SAP Note 3798345 and the SAP Security Patch Day page to identify the fix or mitigation for your release.
- Apply the SAP-provided correction in a test system first, then production, following your normal change process.
- Restrict network access to SAP Gateway ports so only known application servers and administrators can reach them.
- Remove internet exposure of the Gateway unless there is a documented business need.
- Review and tighten Gateway access control lists instead of relying on defaults.
- Check Gateway and network logs for connections from unexpected sources, going back as far as you retain them.
- Record the patch status of each system so you can show the issue is closed.
Detection and monitoring
The research contains no reports of exploitation, and the CISA KEV field is empty. Recheck the CISA KEV catalog and SAP's note over time, and keep monitoring after you patch.
- Alert on new or unexpected source addresses connecting to Gateway ports.
- Watch for changes to Gateway access configuration outside change windows.
- Track SAP's monthly patch day releases and re-check this CVE if SAP updates its note.
- Keep an external view of what you expose: Webforta Monitor can watch certificates, DNS and uptime for your public hostnames, and the free SSL checker is a quick way to review what a public endpoint presents. Neither replaces SAP-specific patching or network review.
For background on filtering traffic in front of business applications, see What is a WAF?. More security news and advisories are collected on the Webforta blog.
What is still unknown
Only one independent publisher covers this story so far, and it is the NVD record itself. The following are not stated in the sources reviewed: the affected SAP Gateway versions, the fixed versions, whether any workaround exists, and whether anyone is exploiting the flaw. Verify each in SAP's note before acting on assumptions.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
