Skip to main content
Mallory
CriticalVulnerability

CVE-2026-89103: PROXYGATE

Published Nov 10, 2026 · Updated today
Trending this week#92of 427,955 vulnerabilities
Mention activity · 30 days54 mentions · peak 35 in a dayToday
CVSS10.0Critical · v3.1
EPSS0.32%26th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-89103CWE-863 · Incorrect Authorization

PROXYGATE is an incorrect-authorization vulnerability in the RFC and CPI-C communication layer of SAP Gateway. Excessively privileged default access-control behavior can cause crafted requests from an external, unauthenticated peer to be classified as originating from a trusted internal application server. When the Gateway proxy access policy permits the connection, the attacker can invoke operations intended for internal systems, potentially including operating-system command execution. The affected Gateway component is used in ABAP, AS Java, dual-stack, and standalone deployments. The vulnerability has a CVSS v3.1 base score of 10.0.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can compromise the confidentiality, integrity, and availability of the SAP environment through unauthorized internal function calls and potentially arbitrary operating-system commands. Commands can execute as the SAP installation owner, <sid>adm, exposing business data, stored credentials, and application configuration to theft or modification and enabling service disruption. This does not automatically provide root privileges on the underlying host.

Mitigation

If you can’t patch tonight, do this now.

Restrict SAP Gateway network access to explicitly authorized application servers and integration hosts, excluding the public internet and untrusted user or partner networks. Review proxy access rules and replace permissive policies with explicit least-privilege restrictions. Securing secinfo and reginfo alone is insufficient because exploitation targets the internal-server trust decision. Network isolation and ACL hardening reduce exposure but are not substitutes for the correction and required configuration changes; no official standalone workaround is identified.

Remediation

Patch, then assume compromise.

Apply the Gateway/kernel correction specified in SAP Security Note 3798345, released November 10, 2026, to every affected application server and standalone Gateway. Complete the required manual configuration steps: most affected kernel releases require gw/acl_mode_proxy = 1, together with appropriately restrictive prxyinfo rules. Consult FAQ Note 3810197 and the applicable correction instructions for release-specific requirements, minimum fixed patch levels, and restart procedures. Upgrade unsupported kernels to a maintained, compatible release. Verify both the installed correction and effective proxy policy; patching alone may leave permissive legacy behavior active. Exact fixed kernel patch levels are not available in the supplied information.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
FAQ

Frequently asked questions

Is CVE-2026-89103 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-89103 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-89103?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-89103.
Is there a patch for CVE-2026-89103?
Apply the Gateway/kernel correction specified in SAP Security Note 3798345, released November 10, 2026, to every affected application server and standalone Gateway. Complete the required manual configuration steps: most affected kernel releases require gw/acl_mode_proxy = 1, together with appropriately restrictive prxyinfo rules.
How severe is CVE-2026-89103?
CVE-2026-89103 has a CVSS v3.1 score of 10.0 (Critical) and an EPSS score of 0.32% (26th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

54 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+23 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity21Community discussion across Reddit, Mastodon, and other social sources.