Two critical bulletins in five weeks: my Adobe Commerce patch runbook

Step 1 of 5

TL;DR

  • Adobe Commerce needs two separate fixes: the APSB26-146 hotfix for CVE-2026-75650 (September 2026, CVSS 10, exploited) and the APSB26-153 patches (13 October 2026).
  • The October patches don't include the September hotfix. Apply both.
  • My runbook has five steps: record what you run, read the bulletin, apply through version control, prove it on staging, then look for an earlier break-in.

CVSS 10. No authentication required. Exploited in the wild. That was APSB26-146 in September 2026: CVE-2026-75650, a template-injection flaw in Adobe Commerce. Five weeks later APSB26-153 shipped patches for every release line Adobe still patches, and the trap is right there in the bulletin: the October patches don't include the September hotfix. If you applied only the latest bulletin, you're still exposed to the worst one.

In September and October 2026, patching for both bulletins took about a week end to end. The patches themselves were quick. Two third-party extensions had to be updated before they would run on the patched release, and that's where the days went.

This is the runbook I use for every bulletin. The steps themselves take about an hour per environment, most of it waiting on deploys. For a full version bump rather than a patch, composer why-not names the packages whose constraints block it.

You’ll need

  • Shell access to a staging copy of production
  • The bulletin page and its patch files from Adobe
  • Composer and the Quality Patches Tool (magento/quality-patches)
  • A smoke-test list, or better, automated checks

Record exactly what you run

The patch level matters more than the minor version. Capture the full version and every patch already applied.

bin/magento --version
composer show magento/product-community-edition magento/product-enterprise-edition 2>/dev/null
vendor/bin/magento-patches status | grep -i applied

On Adobe Commerce on cloud infrastructure, use php ./vendor/bin/ece-patches status, the same command the staging step below uses.

Tip: Paste the output into the ticket. Next month you'll start from facts instead of an SSH session.

Read the bulletin as a checklist

Four fields decide your urgency: affected versions, priority, whether Adobe reports active exploitation, and the fix type (full release, isolated patch or hotfix). For the September and October 2026 bulletins:

  • APSB26-146: critical, priority 1, exploited. Affects Adobe Commerce 2.4.4 to 2.4.9-2026-aug, B2B 1.3.3 to 1.5.3, and Magento Open Source 2.4.6 to 2.4.9-2026-aug. Fixed by a dedicated hotfix for CVE-2026-75650.
  • APSB26-153 (13 October): priority 2, with critical, high and medium fixes and no known exploitation. The fixes ship as isolated patch files for every line from 2.4.4-p18 to 2.4.9, applied on top of the latest -p release. Adobe tells you to apply the APSB26-146 hotfix as well, because it isn't included. Adobe’s knowledge base article says to apply all earlier monthly isolated patches first, in order.

"Exploited" plus "no authentication" means you patch this week, not next sprint. Both bulletins and the PHP fix are in one list in the October 2026 patch check.

Apply patches through version control

Patching a server by hand is an anti-pattern: the next deploy silently reverts it. Commit the patch files and apply them in the build, so every environment ends up identical.

mkdir -p m2-hotfixes && cp ~/Downloads/*.patch m2-hotfixes/
git add m2-hotfixes && git commit -m "Security: APSB26-146 hotfix"

On Adobe Commerce on cloud infrastructure, patches in m2-hotfixes/ apply on deploy. Elsewhere, apply them in your build step with patch -p1 or the cweagans/composer-patches plugin.

The October fix goes in the same folder. There is no Composer release for APSB26-153. Each line gets a ZIP of patch files, and you commit only the ones for the components you run; the hotfix is a separate file next to them. On cloud infrastructure, Adobe says the latest cloud-patches update may already include the fix: check its release notes before adding the ZIP, because Adobe warns that applying the same fix twice can make the install fail.

Deploy to staging and prove the patch landed

Confirm the patched files really changed, then run smoke tests across the paths that earn money: search, product page, add to cart, checkout with a test payment, customer login, and the admin. On Adobe Commerce on cloud infrastructure, ece-tools reports every patch it knows about. Run it on staging after the deploy:

php ./vendor/bin/ece-patches status

Your m2-hotfixes/ files show up as type Custom, and each one should say Applied. N/A means ece-tools can't tell, usually because of a conflict, so treat it as not proven. Outside cloud infrastructure, or as a second check, confirm that the patches reverse cleanly:

git apply --check --reverse m2-hotfixes/*.patch && echo "patches present"

Tip: If a patch "applied" but won't reverse cleanly, something else already modified those files. Stop and find out what before production.

Ship, then look for an earlier break-in

For a flaw exploited before the fix existed, patching locks the door but doesn't check who's already inside. Look for admin users nobody recognises, recently changed PHP files under pub/ and app/, and unfamiliar scripts in CMS blocks.

find pub app -type f -mtime -30 -name '*.php' | head -50

Done!

You now have a runbook to reuse for every bulletin. Next: PHP2Shell, the other urgent fix, the one in PHP itself.

Written by Vishwas Bhatnagar

Technical Architect. Adobe Commerce, marketplaces and AI-assisted engineering.

More about me →

More