Once a month, SAP security teams get a list of fixes and a familiar question: which of these do we install this week, and which can wait? SAP Patch Day is the date that list arrives. If your team treats it as a monthly routine with clear deadlines, most SAP vulnerabilities never become incidents. If it’s handled ad hoc, the backlog grows quietly until an auditor or an attacker finds it.
SAP Security Patch Day is the second Tuesday of every month, when SAP publishes its security notes for on-premises and many cloud-connected products. Each note fixes one vulnerability, carries a CVSS score and a priority, and is downloaded from SAP for Me. Customers decide which notes apply and install them according to their own deadlines.
In one sentence: SAP Patch Day is the second Tuesday of each month, when SAP releases security notes that customers must check against their systems and install by priority.
Key takeaways
- Patch Day falls on the second Tuesday of every month; the next one in 2026 is December 8.
- Note priority comes from the CVSS v3 score; the top band, 9.0 to 10.0, is now labeled Critical (formerly HotNews).
- November 10, 2026 brought 35 new notes, including four rated CVSS 10.0.
- CVSS measures the flaw, not your exposure, so internet-facing systems go first.
- A written deadline policy is what turns Patch Day from a reading exercise into a control.
When is SAP Patch Day?
SAP releases security notes on the second Tuesday of each month, the same rhythm Microsoft and other large vendors follow. SAP’s security notes page lists planned dates in advance. For late 2026 those are October 13, November 10 and December 8.
Urgent fixes can still appear between Patch Days. SAP’s monthly pages add a line when a note is released or updated after the scheduled date, and news coverage of the next Patch Day sometimes counts those notes again. Subscribe to SAP’s notifications so an out-of-cycle fix doesn’t wait four weeks for your next review.
What does SAP publish on Patch Day?
SAP posts a public bulletin with a table of note numbers, titles, affected products and versions, priorities and CVSS scores. The notes themselves sit behind a login in SAP for Me. The bulletin usually contains three kinds of entries:
- New security notes for vulnerabilities fixed this month.
- Updates to earlier notes, which may add affected versions, new correction instructions or only text changes.
- Advisories for open source or SDK components, published through channels such as GitHub.
SAP also separates Patch Day security notes, which deserve attention now, from support package security notes, which arrive automatically when you apply the next support package. Most teams only triage the first group each month.
How does SAP rate the priority of a security note?
SAP calculates note priority from the CVSS v3 base score. SAP’s 2026 bulletins label the top band Critical; older bulletins, and many internal policies, still call it HotNews. The bands are:
| Priority | CVSS v3 score | What it usually means for you |
|---|---|---|
| Critical (HotNews) | 9.0 to 10.0 | Remote, often unauthenticated, full compromise possible. Plan an emergency change. |
| High | 7.0 to 8.9 | Serious impact, often needs some access. Fix within weeks. |
| Medium | 4.0 to 6.9 | Limited impact or harder to exploit. Next maintenance window. |
| Low | 0.1 to 3.9 | Minor. Usually handled with support packages. |
Treat the score as a starting point. A Medium note in a component that faces the internet can matter more than a High note on a system that only three administrators can reach.
What happened on the November 2026 Patch Day?
November 10, 2026 was one of the heaviest releases of the year. SAP’s bulletin listed 35 new security notes, four GitHub advisories and three updates to older notes. Nine entries were rated critical, and four of them carried the maximum CVSS score of 10.0:
| SAP Note | Component | Why it matters |
|---|---|---|
| 3778530, 3778556, 3798345, 3849308 | NetWeaver AS ABAP Internet Communication Manager, SAP Web Dispatcher, SAP Gateway and the AS ABAP SAML2 service provider | Reachable over the network without a valid account, according to SAP and the security firms that analyzed the notes |
As of the release date, none of the November flaws were in CISA’s Known Exploited Vulnerabilities catalog, and Onapsis reported no active exploitation. That’s good news, not a reason to wait. Web Dispatcher and ICM are exactly the components that face users and the internet, so they’re where attackers look first. For component-level advice, see the public analyses linked in the sources below.
Why can’t SAP patches wait for the next upgrade?
Because attackers move faster than upgrade projects. The clearest recent example is CVE-2025-31324 in SAP NetWeaver Visual Composer, scored CVSS 10.0. It let unauthenticated attackers upload files to the server. Researchers saw exploitation before the fix was widely applied, and CISA added it to the Known Exploited Vulnerabilities catalog on April 29, 2025. US federal agencies were given three weeks to patch it.
The lesson for Patch Day planning: a CVSS 10.0 note on an exposed Java or ABAP stack should be treated as an incident in waiting, even when nobody has reported exploitation yet.
How should you process SAP Patch Day each month?
- Read the bulletin on the day. List every Critical and High note and the products it names.
- Check relevance against your inventory. SAP Solution Manager or SAP Cloud ALM System Recommendations compare notes with your actual component versions. Without them, match the bulletin’s product and version lines by hand.
- Rank by exposure. Internet-facing systems, Web Dispatcher, Gateway and Java stacks first; isolated test systems last.
- Apply or work around. Many notes can be implemented with
SNOTE; kernel and Java fixes need patches. If you can’t patch in time, use the note’s workaround and record it. - Test and move. Run focused regression tests, then transport through the landscape.
- Record evidence. Keep the note number, the decision, the date implemented and who approved it. Auditors will ask.
What deadlines should a patch policy set?
SAP doesn’t set deadlines for customers, so you need your own. A common pattern looks like this:
| Priority and exposure | Example deadline |
|---|---|
| Critical on an exposed system | Within days, as an emergency change |
| Critical on an internal system | Within two weeks |
| High | Within 30 days |
| Medium | Next maintenance window |
| Low | With the next support package |
Get management to approve the policy, and agree a standing emergency window with the business in advance. Then a Critical fix doesn’t start a new negotiation every month. Anything you can’t meet goes into a documented exception with an owner and an end date.
Frequently asked questions
What day is SAP Patch Day?
The second Tuesday of every month. The remaining 2026 date is December 8, and SAP publishes future dates on its security notes page.
What is a HotNews note in SAP?
HotNews was the name of SAP’s highest note priority, which recent bulletins call Critical. For security notes it means a CVSS v3 score between 9.0 and 10.0, and it normally needs immediate action.
Where can I download SAP security notes?
The monthly bulletin is public on SAP’s support site, but the notes and correction instructions are in SAP for Me, which needs an S-user login.
Do SAP cloud products need Patch Day work?
SAP patches its SaaS products itself, but customer-managed parts still need you. Examples include on-premises connectors, SDKs used in your BTP applications and the ABAP systems your cloud services connect to.
The bottom line
SAP Patch Day is predictable: the second Tuesday, a public bulletin and notes in SAP for Me. What separates secure SAP shops from the rest is what happens next, meaning a same-day read, an inventory check, exposure-based ranking and deadlines everyone has agreed to. If you’re still building the basics, start with what SAP Basis does and how SAP GRC fits in.
Sources: SAP Security Patch Day, November 2026; BleepingComputer: SAP patches four maximum-severity flaws; ERP Today: November 2026 Patch Day; Onapsis: active exploitation of CVE-2025-31324.


