The Daily Byte
Breaking
Welcome to The Daily Byte — real stories from across Pakistan.
Saturday, 21 November 2026 · Pakistan

The Daily Byte

Stories from Pakistan that deserve to be heard

CVE-2026-89103: SAP PROXYGATE flaw scores maximum 10.0

By The Daily Byte ·15 Nov 2026 ·4 min read
SAP headquarters building in Walldorf, Germany

SAP has patched a flaw in its NetWeaver Gateway that researchers have named PROXYGATE, a pre-authentication vulnerability rated the maximum CVSS score of 10.0. Tracked as CVE-2026-89103, it can allow an unauthenticated attacker with network access to run operating system commands as the account that owns the SAP installation — effectively full control of the system.

The flaw was fixed as part of SAP's November Security Patch Day on 10 November, which addressed 35 vulnerabilities. Four of them carry the maximum CVSS score of 10.0, meaning unauthenticated attackers could exploit them remotely to fully compromise the targeted systems. Alongside PROXYGATE, the four include two memory corruption flaws grouped under the name ICM2SHELL — CVE-2026-76964 in the Internet Communication Manager and CVE-2026-89126 in the Web Dispatcher — and a missing authentication flaw in the SAML2 Service Provider, CVE-2026-120017.

Three of the four flaws, including PROXYGATE, were found and reported by the Onapsis Research Labs, an SAP security firm. SAP issued Security Note 3798345 for the Gateway flaw, with a supporting FAQ note, 3810197.

How PROXYGATE works

The SAP Gateway is the component other systems use to make RFC calls to an SAP system, and it can start helper programs on the host when the system needs them. It runs by default on every NetWeaver ABAP application server, and the same component also runs in AS Java and dual-stack systems and as a standalone gateway.

The Gateway relies on access-control lists to decide what it will do. Two of them, secinfo and reginfo, are the ones nearly every SAP security review checks. PROXYGATE turns on a third, less examined list: prxyinfo, the proxy access control list, which decides which connections the Gateway may relay on behalf of a client.

According to Onapsis, the flaw lives in the Gateway's CPI-C layer. Where the proxy policy allows it, a specially crafted series of requests lets an outside attacker who has not authenticated to anything make the Gateway believe the request comes from one of the system's own internal application servers. From that point, the access-control lists behave exactly as configured — and the rule says allow internal, so the request is allowed. The Gateway then starts what the attacker asked for, and in the most severe form that is an arbitrary operating system command running as <sid>adm.

Nothing in the chain requires an SAP user, a password or a certificate, and the hardened secinfo and reginfo lists play no part in stopping it. The <sid>adm account owns the SAP installation: its executables, its instance profiles, its secure store and its connection to the database. An attacker running commands as that user could recover database credentials, read or modify business data, move laterally to connected systems, or stop the SAP system altogether.

Patching alone is not enough

What makes PROXYGATE unusual is that a version check, or even a patch, does not by itself establish whether a system is safe. Because the flaw is in the SAP kernel, it affects a broad range of releases, including kernel versions that are already out of maintenance. But whether it can actually be exploited is decided by the Gateway's proxy policy.

A Gateway with a restrictive prxyinfo file is not exploitable from untrusted networks. Several other configurations leave the proxy policy open, and some of them are defaults. Where no prxyinfo file exists at all, the outcome depends on the profile parameter gw/acl_mode_proxy, which ships disabled for backward compatibility — meaning allow-all.

SAP's fix therefore has two parts: the kernel patch from Security Note 3798345, and setting gw/acl_mode_proxy to 1. Kernels 7.93 and 9.16 already support the parameter, while kernels 7.22, 7.53, 7.54, 7.77, 8.04, 9.20 and 9.21 gain support with the patch. Out-of-maintenance kernels, including 7.20, 7.21 and the 7.40 to 7.89 range, must be upgraded to a downward-compatible kernel that is still in maintenance.

Onapsis advises restricting any permissive prxyinfo file first, starting with gateways reachable from the internet, then applying the kernel patch and the parameter. It also advises narrowing network access to the Gateway ports, 33NN and 48NN, to the hosts that genuinely need RFC access. As of its publication, Onapsis said it had not observed active exploitation of the flaw in the wild.

Sources: Onapsis Research Labs advisory; BleepingComputer.