Multiple Vulnerabilities in SAP Products Could Allow for Arbitrary Code Execution

Multiple vulnerabilities have been discovered in SAP Products, the most severe of which could allow for arbitrary code execution. 

• SAP NetWeaver is SAP’s technology platform and application server stack (ABAP and Java) that underpins many SAP business applications, including ERP and S/4HANA.
• SAP Web Dispatcher is a software load balancer and reverse proxy that receives web requests from the internet and forwards them to SAP application servers.
• SAP Gateway is the component that exposes SAP data and business logic through OData services and manages RFC communication between SAP systems and external applications.
• SAP ABAP Developer Tools is an eclipse-based development environment for writing, testing, and debugging ABAP code in SAP systems.
• S4CRM is the customer relationship management software for SAP S/4HANA, covering sales, service, and marketing processes.
• SAP Cloud SDK is a set of developer libraries (for languages such as Python and JavaScript) that simplify building applications that connect to SAP cloud services and AI capabilities.

Successful exploitation of the most severe of these vulnerabilities could allow the attacker to execute arbitrary code and fully compromise the system, resulting in a high impact on confidentiality, integrity and availability of the system.

There are currently no reports of these vulnerabilities being exploited in the wild. 

Multiple vulnerabilities have been discovered in SAP Products, the most severe of which could allow for arbitrary code execution. Details of these vulnerabilities are as follows: 

Tactic: Initial Access (TA0001)

Technique: Exploit Public-Facing Application (T1190)

Memory Corruption Vulnerability in SAP NetWeaver AS ABAP (Internet Communication Manager) (CVE-2026-76964)

• Memory Corruption vulnerability in SAP Web Dispatcher (CVE-2026-89126)
• Broken Access Control in SAP Gateway (CVE-2026-89103)
• Missing Authentication in SAP NetWeaver AS ABAP and ABAP Platform (SAML2 Service Provider) (CVE-2026-120017)
• Code Injection vulnerability in SAP NetWeaver Knowledge Management (XML Forms) (CVE-2026-109803)
• OS Command Injection vulnerability in ABAP Application Server for SAP NetWeaver and ABAP Platform (CVE-2026-76965)
• Missing authorization check in S4CRM (CVE-2026-109795)
• Cross-Site Request Forgery (CSRF) vulnerability in SAP Web Dispatcher and Internet Communication Manager (CVE-2026-89119, CVE-2026-120014)
• XML External Entity (XXE) Vulnerability in SAP BusinessObjects Business Intelligence Platform (Web Intelligence) (CVE-2026-109798)
• Multiple vulnerabilities in Application Server ABAP of SAP NetWeaver and ABAP Platform (CVE-2026-76966, CVE-2026-109796)
• Memory Corruption Vulnerability in SAP NetWeaver (Internet Graphics Service) (CVE-2026-120008)
• Memory Corruption vulnerability in SAP Web Dispatcher (CVE-2026-109800)
• Improper verification of JWT signature in IASContextProvider leads to tenant/user identity spoofing in SAP Cloud SDK for Python (CVE-2026-109799)
• Denial of Service (DoS) vulnerability in SAP NetWeaver Application Server ABAP (Internet Communication Manager) and SAP Web Dispatcher (CVE-2026-109793)
• Memory Corruption vulnerability in SAP NetWeaver Application Server (SAP Message Server) (CVE-2026-120010)
• Multiple Vulnerabilities in SAP NetWeaver (Internet Graphics Service) (CVE-2026-109806, CVE-2026-109807)
• Memory Corruption vulnerability in Application Server ABAP for SAP NetWeaver and ABAP Platform (CVE-2026-76970)
• Information Disclosure in SAP NetWeaver (SAP Message Server) (CVE-2026-109804)
• Missing Authentication check in SAP NetWeaver AS Java EDM Application (CVE-2026-89114)
• Memory Corruption vulnerability in Application Server ABAP of SAP NetWeaver and ABAP Platform (SAP Message Server) (CVE-2026-76973)
• Denial of Service vulnerability in SAP NetWeaver Application Server ABAP, ABAP Platform and SAP Web Dispatcher (CVE-2026-109794)
• Path Traversal in Agent Memory Module of SAP Cloud SDK for Python (CVE-2026-120013)
• Information Disclosure vulnerability in SAP Cloud SDK for AI (JavaScript) (CVE-2026-120012)
• Insufficient Input Validation in SAP Host Agent (CVE-2026-120015)
• Code Injection vulnerability in SAP ABAP Developer Tools (AMDP Data Preview) (CVE-2026-120009)
• Cross-tenant sandbox takeover in SAP/astonish (CVE-2026-109797)
• Denial of Service (DoS) vulnerability in SAP NetWeaver Application Server for ABAP (CVE-2026-109802)
• Server-Side Request Forgery (SSRF) vulnerability in SAP NetWeaver and ABAP Platform (Application Server ABAP) (CVE-2026-109811)
• Security Vulnerabilities in SAP NetWeaver Application Server Java (NWDI Cockpit) (CVE-2026-109801, CVE-2026-109809)
• Weak Cryptography in SAP NetWeaver and ABAP Platform (Application Server ABAP) (CVE-2026-109805)
• Cross-Site Scripting (XSS) vulnerability in SAP NetWeaver Visual Composer (CVE-2026-120016)
• CSS Injection vulnerability in SAP NetWeaver Application Server Java (Web Dynpro Java) (CVE-2026-109810)
• Insecure Storage of Sensitive Information in SAP Web Dispatcher and Internet Communication Manager (CVE-2026-89125)
• Server-Side Request Forgery in SAP NetWeaver AS Java (Web Services) (CVE-2026-89129)
• Cross-Site Scripting (XSS) vulnerability in SAP NetWeaver Application Server ABAP (Applications based on SAP GUI for HTML) (CVE-2026-76976)
• Broken Access Control in SAP NetWeaver Process Integration (Process Integration Test Tool) (CVE-2026-89128)
• Denial of Service (DoS) in SAP Business Objects (CVE-2026-73635)
• Information Disclosure vulnerability in SAP Start Service and SAP Microsoft Management Console (CVE-2026-89115)
• Cross Site Request Forgery (CSRF) vulnerability in SAP NetWeaver Enterprise Portal (CVE-2026-89131)
• Security misconfiguration in SAP WebClient UI (CVE-2026-44768)
• Missing Authorisation Check in SAP Solution Tools Plug-In (ST-PI) (CVE-2026-109808)

Successful exploitation of the most severe of these vulnerabilities could allow the attacker to execute arbitrary code and fully compromise the system, resulting in a high impact on confidentiality, integrity and availability of the system.

We recommend the following actions be taken:

• Apply appropriate updates provided by SAP to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
• Safeguard 7.1: Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
• Safeguard 7.2: Establish and Maintain a Remediation Process: Establish and maintain a risk-based remediation strategy documented in a remediation process, with monthly, or more frequent, reviews.
• Safeguard 7.4: Perform Automated Application Patch Management: Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.
• Safeguard 7.7: Remediate Detected Vulnerabilities: Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process.
• Safeguard 12.1: Ensure Network Infrastructure is Up-to-Date: Ensure network infrastructure is kept up-to-date. Example implementations include running the latest stable release of software and/or using currently supported network-as-a-service (NaaS) offerings. Review software versions monthly, or more frequently, to verify software support.

• Vulnerability scanning is used to find potentially exploitable software vulnerabilities to remediate them. (M1016: Vulnerability Scanning)
• Safeguard 16.13: Conduct Application Penetration Testing: Conduct application penetration testing. For critical applications, authenticated penetration testing is better suited to finding business logic vulnerabilities than code scanning and automated security testing. Penetration testing relies on the skill of the tester to manually manipulate an application as an authenticated and unauthenticated user.
• Safeguard 18.1: Establish and Maintain a Penetration Testing Program: Establish and maintain a penetration testing program appropriate to the size, complexity, and maturity of the enterprise. Penetration testing program characteristics include scope, such as network, web application, Application Programming Interface (API), hosted services, and physical premise controls; frequency; limitations, such as acceptable hours, and excluded attack types; point of contact information; remediation, such as how findings will be routed internally; and retrospective requirements.
• Safeguard 18.3: Remediate Penetration Test Findings: Remediate penetration test findings based on the enterprise’s policy for remediation scope and prioritization.

• Apply the Principle of Least Privilege to all systems and services. Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack. (M1026: Privileged Account Management)
• Safeguard 4.7: Manage Default Accounts on Enterprise Assets and Software: Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.
• Safeguard 5.5: Establish and Maintain an Inventory of Service Accounts: Establish and maintain an inventory of service accounts. The inventory, at a minimum, must contain department owner, review date, and purpose. Perform service account reviews to validate that all active accounts are authorized, on a recurring schedule at a minimum quarterly, or more frequently.

• Architect sections of the network to isolate critical systems, functions, or resources. Use physical and logical segmentation to prevent access to potentially sensitive systems and information. Use a DMZ to contain any internet-facing services that should not be exposed from the internal network. Configure separate virtual private cloud (VPC) instances to isolate critical cloud systems. (M1030: Network Segmentation)
• Safeguard 12.2: Establish and Maintain a Secure Network Architecture: Establish and maintain a secure network architecture. A secure network architecture must address segmentation, least privilege, and availability, at a minimum.
• Safeguard 12.8: Establish and Maintain Dedicated Computing Resources for All Administrative Work: Establish and maintain dedicated computing resources, either physically or logically separated, for all administrative tasks or tasks requiring administrative access. The computing resources should be segmented from the enterprise's primary network and not be allowed internet access.