SOCLYDE logo
Current languageEN
Cybersecurity newsCybersecuritysap

SAP patches flaws that bypass authentication

SAP’s November updates address ICM2SHELL and PROXYGATE. Prioritize component inventories, Gateway proxy settings and evidence for each installation.

Published on

By Soclyde Team

An empty business operations office overlooks an idle manufacturing workshop

In summary

  • ICM2SHELL and PROXYGATE can enable unauthenticated command execution.
  • PROXYGATE requires checking both the patch and proxy configuration.
  • Onapsis reported no observed active exploitation at publication.

Explore next

Soclyde resources

Article contents

On November 10, 2026, SAP released monthly security updates that address ICM2SHELL and PROXYGATE. These flaws affect components receiving or relaying traffic to business applications. They require action by the SAP administration team beyond changing an end user’s password.

Components ahead of the sign-in screen

SAP’s bulletin rates the affected ICM, Web Dispatcher and Gateway issues critical. ICM2SHELL covers CVE-2026-76964 and CVE-2026-89126; PROXYGATE is CVE-2026-89103. Their discoverer, Onapsis, describes paths to command execution without credentials.

BleepingComputer explains how these components connect external applications with SAP systems. For a small company relying on an integrator, the first question is who administers those components and can confirm their condition. Access to a business portal does not necessarily include control of the infrastructure underneath it.

Two flaws with different remediation requirements

Onapsis says ICM2SHELL involves WebSocket handling in kernel code shared by ICM and Web Dispatcher. Exposure can exist even when applications do not intentionally use WebSocket. The research reported no observed active exploitation at publication.

For PROXYGATE, Onapsis distinguishes the kernel vulnerability from the prxyinfo proxy policy. On most kernel releases, remediation combines a patch with gw/acl_mode_proxy = 1. Restrictive secinfo and reginfo lists alone do not establish that this particular path is closed.

Request evidence for every installation

Have ICM, Web Dispatcher and Gateway inventoried, including standalone instances. Ask your Basis team to map each component to its SAP note, applicable patch level and settings to verify. Version requirements and prerequisites must come from the notes matching your installation.

SecurityWeek distinguishes new notes, updated notes and GitHub advisories within the November release. That context helps avoid reducing the task to a headline count of fixed flaws. The evidence that matters to your organization is the result on each instance you operate.

Plan the return of business operations

For invoicing or manufacturing workflows dependent on SAP, agree a maintenance window with a business owner. After the intervention, test a representative operation using a suitable account and confirm that network restrictions remain in place.

If there are signs of compromise, involve your response team before treating the patch alone as recovery. Preserve material needed for investigation and identify service accounts or secrets that need renewal from a trusted environment.

The connection with Soclyde

Soclyde’s encrypted local vault can organize credentials for the integrator, support portals and business services. Soclyde Premium allows access sharing within a team without scattering copies through messages. These functions do not patch the SAP kernel or configure Gateway rules; administering those components remains a separate task.

What to remember

Request the mapping between instances, fixes and proxy settings, then verify business operations after maintenance. To organize access used with your SAP provider, talk to the Soclyde team.

Frequently asked questions

Will a stronger SAP password be enough?

No. The described paths can be reached without authentication. Your SAP team must apply the relevant notes and check network exposure.

Is installing the Gateway patch enough?

Not necessarily. Onapsis says most kernel releases require the patch together with gw/acl_mode_proxy = 1. Have your Basis team validate the procedure for your installation.

Are these flaws already being exploited?

Onapsis reported no observed active exploitation when it published its November 10 research. Patching remains necessary, and this observation does not rule out attacks elsewhere.

References

Sources and references

Need advice?

Design your password strategy with Soclyde

Schedule a dedicated walkthrough with the team to see how local-first security adapts to your stack.

Talk with us

Keep reading