Adobe Commerce Security Patches Before Black Friday: What Store Teams Should Do Now

Adobe Commerce security patches before Black Friday: the October security update, the September hotfix and the 10 November Cloud Service release, by WeVerve Systems

Adobe Commerce Security Patches Before Black Friday: What Store Teams Should Do Now

If your store runs on Adobe Commerce or Magento Open Source, the weeks before Black Friday are usually about locking things down: no new extensions, no big theme changes, and as few deployments as possible. This year there is a catch. Adobe has shipped a critical hotfix for a vulnerability that attackers are already using, a regular security update with several critical fixes, and, for stores on its SaaS edition, a platform release that reaches Production today, 10 November 2026.

None of these should wait until January. This guide explains which Adobe Commerce security patches and releases apply to your setup, what each one changes, and how to fit the work into the time left before Black Friday on 27 November.

Key takeaways

  • Adobe released a hotfix for CVE-2026-75650 on 7 September 2026 (bulletin APSB26-146). Adobe says the flaw has been exploited in the wild, and it allows an unauthenticated attacker to run code on an affected store.
  • The October security update (APSB26-153, 13 October) fixes critical, high and medium issues across Adobe Commerce 2.4.4 to 2.4.9 and Magento Open Source 2.4.6 to 2.4.9. Adobe asks you to apply the September hotfix in addition to it.
  • After the hotfix, Adobe says to rotate your encryption key and every credential it may have exposed, including integration tokens and payment gateway keys at the provider.
  • Adobe Commerce as a Cloud Service gets its November release in Production on 10 November. Non-virtual orders created through two REST endpoints now need a shipping address or the request fails with HTTP 400.
  • Patch and test on staging this week, deploy before your code freeze, and keep peak week for monitoring rather than changes.

First, check which Adobe Commerce setup you run

Adobe Commerce now comes in several forms, and the work is different for each. Before you plan anything, confirm which one you are on and the exact version string, for example 2.4.7-p9 or 2.4.8-2026-sep.

SetupWho applies updatesWhat to do before Black Friday
Adobe Commerce on-premisesYour team or agencyApply the October update and the September hotfix, rotate credentials, test
Adobe Commerce on cloud infrastructure (PaaS)Your team or agency, deployed through GitSame as on-premises, then confirm the hotfix shows as Applied
Magento Open SourceYour team or agencyApply the October update and the September hotfix, rotate credentials, test
Adobe Commerce as a Cloud Service (SaaS)AdobeTest integrations against the 10 November release and watch emails
Sources: Adobe security bulletins APSB26-146 and APSB26-153, Adobe Commerce as a Cloud Service release notes.

Adobe’s Cloud Service release notes point stores on-premises and on cloud infrastructure to the regular Adobe Commerce release notes instead, so the November release section below only applies to the SaaS edition.

The September hotfix you cannot skip

On 7 September 2026, Adobe published security bulletin APSB26-146 for CVE-2026-75650, a template engine flaw rated critical with a CVSS base score of 10.0. No login is needed to exploit it, and Adobe states that it is aware of the vulnerability being exploited in the wild against Adobe Commerce merchants.

Who is affected

  • Adobe Commerce 2.4.4 to 2.4.9, up to and including the 2026-aug builds.
  • Adobe Commerce B2B 1.3.3 to 1.5.3.
  • Magento Open Source 2.4.6 to 2.4.9.

The fix ships as a hotfix (VULN-39341), not as a full release. Adobe’s knowledge base article lists the right patch file for each version, from 2.4.4 to the current 2.4.9 builds. If your store is on an older patch level, check that table rather than assuming the latest file fits.

Rotate credentials after patching

Patching closes the hole, but it does not undo anything an attacker may already have taken. Adobe’s guidance is to rotate the encryption key and all credentials that may have been encrypted or exposed with it. The key protects integration tokens, payment gateway credentials and system automation tokens. Adobe’s list includes:

  • Rotating the encryption key and all Admin user passwords.
  • Deactivating and regenerating REST, SOAP and GraphQL integration tokens under System > Extensions > Integrations.
  • Rotating OAuth client secrets for connected third-party apps.
  • Rotating payment gateway API credentials at the provider, such as Stripe, Braintree, Adyen or PayPal, not only inside Commerce.
  • Rotating database and Fastly credentials, SSH and deploy keys, and API keys for shipping, tax and other extensions.

Adobe recommends doing this in maintenance mode with cron disabled. Plan a short, announced window, and have every vendor login ready before you start, because a payment or shipping key you cannot reissue quickly will hold up the whole store.

The October security update

On 13 October 2026, Adobe released APSB26-153, a priority 2 update that fixes vulnerabilities rated critical, high and medium. The impacts listed include arbitrary code execution, privilege escalation, arbitrary file system write and security feature bypass. Adobe says it is not aware of exploits in the wild for these issues, but several of them need no authentication, so they are worth closing before peak traffic.

Versions to move to

  • Adobe Commerce: 2.4.9-2026-oct, 2.4.8-2026-oct, 2.4.7-2026-oct, 2.4.6-2026-oct, 2.4.5-2026-oct or 2.4.4-2026-oct.
  • Adobe Commerce B2B: 1.5.3-2026-oct, 1.5.2-2026-oct, 1.4.2-2026-oct, 1.3.4-2026-oct or 1.3.3-2026-oct.
  • Magento Open Source: 2.4.9-2026-oct, 2.4.8-2026-oct or 2.4.7-2026-oct.

The bulletin also lists 2.4.10-alpha1, the first alpha of the next release line. That is not something to put on a live store before Black Friday.

A note for cloud infrastructure projects

Adobe’s Cloud Patches for Commerce package applied the APSB26-153 fixes in version 1.1.22 on 13 October. Version 1.1.23 followed on 19 October with extra safeguards in the October isolated patch for 2.4.8-p5. If you are on 2.4.8-p5, make sure your project uses the newer package.

How to patch safely before peak

The order of work matters more than the speed. A rushed patch that breaks checkout is worse than a day’s delay.

Five step Adobe Commerce patch flow: copy production to staging, apply the October security update and the September hotfix, verify patch status, rotate the encryption key and credentials, then test checkout, order sync, emails and admin login before deploying
A safe order of work for patching Adobe Commerce or Magento Open Source before peak season.

Step 1: Prepare staging

  • Copy production code and a recent database to staging, so you test against real extensions and data.
  • List every third-party module and custom integration, with a named owner for each.

Step 2: Apply and verify

  • Apply the October update for your version, then the September hotfix if your build still needs it.
  • On cloud infrastructure, use the Quality Patches Tool to confirm the hotfix shows an Applied status, as Adobe’s article describes.

Step 3: Test what earns money

  • Place test orders with every payment method, including saved cards and express wallets.
  • Check that orders, stock and prices still sync with your ERP, warehouse and marketplaces.
  • Confirm order, shipping and password emails send, and that Admin login and two-factor work.
Pre Black Friday Adobe Commerce checklist: confirm your exact version, apply the October security update, apply the September hotfix, rotate the encryption key and secrets, regenerate integration tokens, test checkout with every payment method, check ERP and order sync calls, and watch alert and reminder emails
Eight checks that cover the October update, the September hotfix and the November release.

The November Cloud Service release

For stores on Adobe Commerce as a Cloud Service, Adobe applies updates for you. The November 2026 release #1 has been in Sandbox environments and reaches Production on 10 November. Most of it is additive, but one change can break existing integrations.

REST orders now need a shipping address

New non-virtual orders created through POST /V1/orders and PUT /V1/orders/create now require a shipping address. Requests without one return an HTTP 400 error. Adobe says this stops orders without shipping information from causing order email failures. If a marketplace connector, POS or ERP creates orders this way, test it now. Adobe gives two options for orders without a shipping address: set is_virtual to 1 for digital-only orders, or place the order from a cart with PUT /V1/carts/:cartId/order.

New options for developers

  • Cart items can carry custom attributes through the addProductsToCart mutation, which suits gift notes, engraving text or B2B references.
  • A new webhook can read and change return data before a return is saved. If a required webhook fails, the return is not saved.
  • A shipment item filter webhook can exclude items that a third party fulfils from new shipments.
  • A new REST endpoint returns a customer’s store credit balance.

Fixes shoppers will notice

  • Price and back-in-stock alert emails were not being sent; that is fixed, so expect alert volume to return.
  • Abandoned cart reminders could send extra emails; that is fixed too.
  • AEM Assets product images could come back without image roles in GraphQL. Adobe says to resync the product data feed for products exported before the fix.

Plan it around your code freeze

With Black Friday on 27 November and Cyber Monday on 30 November, most teams want production changes finished by the middle of the month. A realistic plan looks like this:

  • This week: confirm your setup and version, build staging, and collect vendor logins for credential rotation.
  • Next week: apply and test the October update and the September hotfix, then deploy in a planned window and rotate credentials.
  • Cloud Service stores: test order-creating integrations against the 10 November release and check alert and reminder emails.
  • Peak week: no new modules or theme changes; watch logs, payment errors and order sync instead.
  • After Cyber Monday: review Adobe’s next scheduled security release and plan the next patch cycle.
Timeline of Adobe Commerce updates in autumn 2026: critical hotfix on 7 September, October security update on 13 October, Cloud Service release on 28 October, November Cloud Service release in Production on 10 November, and Black Friday on 27 November
Adobe Commerce security and release dates against Black Friday on 27 November 2026.

How WeVerve helps

WeVerve Systems builds and supports Adobe Commerce and Magento stores, along with the integrations around them, from ERP and inventory sync to payments, marketing and custom modules. We can confirm your exact version, apply and test the October update and the September hotfix on staging, run credential rotation with your vendors, and check your order and payment integrations against the November release. Through peak season, our 24/7 eCommerce support keeps an eye on checkout and syncs so problems are caught early.

If you want a second pair of eyes on your Adobe Commerce store before Black Friday, talk to the WeVerve team.

Sources

ZZTESTZZ
No Comments

Post A Comment