SAP’s September 2026 Security Patch Day, on 8 September, fixed 19 new vulnerabilities and updated one older note. Four of the new notes are rated critical, and the worst, a memory corruption flaw in SAP Extended Passport (EPP) processing, scores the maximum CVSS 10.0. If your organisation has not applied these notes yet, treat them as overdue: the next Patch Day is on Tuesday 13 October 2026.

Key facts

  • Date: 8 September 2026 (SAP releases fixes on the second Tuesday of each month).
  • Notes: 19 new security notes plus 1 update to an August note, according to SAP’s official Patch Day page.
  • Critical: 4 notes, with CVSS scores of 10.0, 9.8, 9.4 and 9.0.
  • Range: CVSS scores run from 2.2 to 10.0.
  • Products hit: SAP kernel components, NetWeaver Message Server, SAP GUI for Java, the SAP Cloud Application Programming Model (CAP), ABAP Developer Tools, Integration Suite, Commerce Cloud, several S/4HANA finance apps and SAPUI5.

Security vendors’ counts can differ from SAP’s. Onapsis, for example, lists 20 new and 2 updated notes with five HotNews items, because its tally includes notes SAP revised after Patch Day, such as an update to the August Commerce Cloud note. SAP’s own page is the reference for compliance records.

The four critical notes

SAP noteProductIssueCVSS
3747649 (CVE-2026-44756)SAP Extended Passport (EPP) processingMemory corruption10.0
3759472 (CVE-2026-58240)SAP NetWeaver Message ServerMissing authentication check9.8
3798315 (CVE-2026-76969)Multitenant apps built on SAP CAP (@sap/cds-mtxs)Credential disclosure9.4
3781729 (CVE-2026-66768)SAP GUI for JavaImproper access control9.0

Extended Passport (3747649) is the one to fix first. EPP is the header SAP uses to trace a request as it passes between systems. Onapsis, which found the flaw and calls it OVERPASS, says a crafted request can trigger memory corruption without any login, and in the worst case lead to operating-system command execution. Reports say it affects the SAP kernel and the standalone Web Dispatcher, so the fix is a kernel patch rather than an ABAP note. Onapsis also reports that a publicly released toolkit now includes proof-of-concept code for this flaw and for the Message Server issue, which raises the urgency.

Message Server (3759472) matters because the message server coordinates logons and load balancing in every ABAP system. If you cannot patch at once, restrict network access to message server ports so only application servers and admin hosts can reach them.

CAP (3798315) affects custom multitenant applications built with SAP’s Node.js CAP framework on BTP. This is a developer fix: update the library and redeploy, then rotate any credentials that may have been exposed.

High-priority notes worth a look

SAP noteProductIssueCVSS
3772411 (update)ABAP Developer ToolsPrivilege escalation8.8
3792978Integration Suite (Trading Partner Management)XML external entity (XXE)8.5
3784138NetWeaver Business ClientInsecure deserialisation7.8
3757002NetWeaver ABAP Application ServerMemory corruption7.7
3791068Commerce Cloud (Search and Navigation)CRLF injection via Jetty7.4

The rest are medium and low priority, including an SQL injection in S/4HANA Intercompany Matching and Reconciliation (6.5), several CSRF and authorisation fixes in S/4HANA finance apps (4.3), a clickjacking fix in SAPUI5 (4.3) and a denial-of-service fix in the Process Integration SOAP adapter (2.2).

Why SAP patching cannot wait

SAP systems hold finance, HR, supply chain and customer data, and attackers move quickly. One recent example: SAP fixed a CVSS 10.0 flaw in the Commerce Cloud Data Hub Adapter (note 3771065, CVE-2026-58231) on its August Patch Day, 11 August 2026, and security firm Field Effect reported exploitation attempts by 14 August, three days later.

In India, CERT-In’s May 2026 cyber security guidance asks organisations to fix known exploited vulnerabilities on internet-facing and critical systems within 12 hours where feasible, with one day for critical externally exposed flaws and three days for critical internal flaws on high-value systems. ERP systems usually count as high-value. Our explainer on CERT-In’s 12-hour patch timeline covers the full set of deadlines.

Checklist for SAP Basis and security teams

  1. Pull the list. Log in to the SAP Support Portal (S-user required) and filter HotNews and High Priority notes for your products and releases.
  2. Map notes to systems. List every production, quality and development system, plus internet-facing pieces such as Web Dispatcher, Fiori, Portal and Commerce. Web Dispatcher is easy to forget and is affected by the EPP flaw.
  3. Patch the kernel first. Plan the EPP kernel update as an emergency change with a short regression test. A kernel swap usually needs a restart, so agree a window with the business.
  4. Use workarounds where patching waits. Restrict message server ports and limit who can reach exposed services, using SAP’s documented workarounds.
  5. Look for signs of attack. Review the Security Audit Log, gateway and message server logs, and Web Dispatcher access logs for unusual requests since 8 September.
  6. Fix custom apps. Ask BTP developers to update CAP libraries, redeploy and rotate secrets.
  7. Record everything. Keep dates, note numbers and approvals for auditors, especially for SOX, RBI or SEBI compliance.

A sample timeline

A mid-sized Indian manufacturer running S/4HANA on premises might plan it like this: day 0, review notes and restrict message server access; days 1-2, kernel update in development and quality; day 3, production kernel update in a weekend window; week 2, ABAP notes and S/4HANA app fixes through the normal transport cycle. If any of the critical systems face the internet, the CERT-In timelines above call for a faster first step.

Before 13 October

October’s Patch Day falls on 13 October 2026. Close out the September critical notes before then, so you are not dealing with two months of fixes at once. If you work on an older ECC system, our guide to SAP ECC maintenance deadlines explains how long security fixes will keep coming.

Career note

SAP security, covering GRC, Basis hardening and vulnerability management for ERP, is a niche with steady demand in Indian GCCs and consultancies. Basis administrators who can read a security note, judge its real risk for their systems and run a clean emergency change are hard to find. Learning SAP’s security tools and an SAP security certification can set you apart.

Sources

Last reviewed: 9 October 2026.

Leave a Reply

Trending