Skip to main content

Neotech Cloud Solutions

Home/Cybersecurity/Magento BlockStrap vulnerability (CVE-2026-103849): the race between the patch and attackers
Personne tenant une carte de crédit devant un ordinateur portable, illustrant la faille Magento BlockStrap qui menace les boutiques en ligne

Magento BlockStrap vulnerability (CVE-2026-103849): the race between the patch and attackers

No password to steal, no click needed: with the Magento BlockStrap vulnerability (CVE-2026-103849), an attacker can run their own PHP code on the server of a Magento or Adobe Commerce online store. Severity score: 10.0 out of 10. From there, they can hide a card skimmer on the checkout page, steal the customer database or install a backdoor.

The good news: as of October 16, no attacks had been seen on live stores. The bad news: security firm Sansec built four ways to exploit it in under 24 hours, and the previous flaw of the same kind was mass-exploited three days after its fix. It’s a race.

The race: patch versus attackers

🛡️ Defense side
🏴‍☠️ Attack side
Adobe releases an emergency fix for StyleSmuggler (CVE-2026-75650), a first critical flaw in the email template engine.
Sep. 2026
+ 3 days
According to Sansec, StyleSmuggler goes from fix to mass exploitation in three days.
Adobe publishes bulletin APSB26-153: BlockStrap, CVSS 10.0. Priority 2, meaning “patch within 30 days”.
Oct. 13
Mage-OS 3.6.0 ships the fix.
Oct. 14
Sansec publishes its analysis and disputes the priority 2 rating.
Oct. 15
Sansec reproduces four routes to code execution in under 24 hours, working from the patch.
BleepingComputer amplifies the warning.
Oct. 16
No attacks seen on live stores… so far.
Is your store patched and verified?
What next?
Sansec expects mass exploitation.

Adobe rated the fix priority 2, which allows 30 days. Sansec disagrees: in its view, anyone with an AI agent can turn the patch into a working attack in a short time. Its advice to merchants is blunt: recall your team from vacation and patch today.

Are you affected by the Magento BlockStrap vulnerability?

It all depends on your store’s platform, and above all on who applies the fixes.

Platform Who applies the fixes Affected by BlockStrap?
Magento Open Source (self-hosted) You, your agency or your host Yes, up to 2.4.9 “2026-sep”
Adobe Commerce and Adobe Commerce B2B You or your integrator Yes, up to 2.4.9 and B2B 1.5.3 “2026-sep”
Mage-OS You or your agency Yes up to 3.5.0, fixed in 3.6.0
WooCommerce, PrestaShop You, your agency or your host No (different software), but same logic: plugins and updates to keep up with
Shopify, Wix, Squarespace (hosted platforms) The platform itself No: not Magento, and the platform applies its own fixes

Not sure what your store runs on? That’s the first question to ask your web agency or host, today.

Two fixes, not one

This is the main trap with this flaw. The October fix doesn’t include the September one: you need both.

🧩

September fix

The StyleSmuggler emergency hotfix VULN-39341, installed first and kept in place.

+

🧩

October fix

A “2026-oct” release (for example 2.4.9-2026-oct) or Adobe’s isolated patch (bulletin APSB26-153).

=

🛡️

Protected store

Against StyleSmuggler and BlockStrap, as long as both are properly applied.

Another trap flagged by Sansec: a plain Composer install keeps the vulnerable base version. You have to explicitly apply the “2026-oct” release or the isolated patch.

Check that the fix actually landed

Deployment pipelines can skip part of a patch without showing an error. Sansec offers a one-line check you can pass as-is to your agency or host:

● ● ●  BlockStrap check (per Sansec)
# In the Magento root folder
$ grep -c resolveDeferredDirectives vendor/magento/framework/Filter/Template.php
✔ 1 or more: the BlockStrap fix is in place
✘ 0: the fix is missing, even if the deployment “succeeded”
# Mage-OS: check vendor/mage-os/framework/Filter/Template.php

30 seconds of work for a clear answer: yes or no, your store is protected.

The plan for the next 24 hours

⏱️

H+0

Know where you stand

  • Confirm your store’s platform and exact version (your agency or host knows).
  • Ask who applies the fixes, and when.

⏱️

H+2

Patch

  • First install the September hotfix VULN-39341 if it’s missing, then the “2026-oct” release or the isolated patch.
  • Magento Open Source 2.4.6 or older: public patches only cover 2.4.7-p10, 2.4.8-p5 and 2.4.9. You need to move to 2.4.7-p10 or later.
  • Can’t patch within the hour? Put the store behind a web application firewall (WAF) with a rule against BlockStrap.

⏱️

H+4

Verify

  • Have the verification command above run.
  • Run a scan for backdoors and card-skimming code.

⏱️

H+24

Monitor

  • Review the store’s administrator accounts and remove any nobody recognizes.
  • Check the scripts loaded on the checkout page.
  • Ask your payment provider to flag any rise in fraud.

⏱️

D+7

Prevent

  • Plan the upgrade if you’re on a version that no longer gets public patches.
  • Set a monthly update routine, with one person responsible.

The lesson, even without Magento

The Magento BlockStrap vulnerability is a reminder of a simple rule: a self-hosted online store is software that needs maintaining like a server. If you don’t know who applies the fixes, how fast and who checks they landed, you’ve found your main risk. And if customer or card data may have been exposed, Quebec’s Law 25 requires you to assess the risk of serious injury and record the incident in your register.

Also read: the 8 questions to ask your web host and how a simple ad installed spyware. For a site that’s maintained and patched, see our website design offer and our cybersecurity services.

Book your free cyber check

Online store, WordPress site, plugins: do you know who applies the fixes, and how fast? The free cyber check reviews your website, your hosting and your access, and gives you a clear action list.

👉 Book your free cyber check

Call us at 438-476-2322 or email info@neotechcloudsolutions.com.

Sources

Photo: Kaboompics, Pexels (Pexels licence).

One thought on “Magento BlockStrap vulnerability (CVE-2026-103849): the race between the patch and attackers”

Leave a Reply

Your email address will not be published. Required fields are marked *