Back to Blog Homepage
    Deploy Blog
    Nathan Chick

    BlockStrap (CVE-2026-103849): Another CVSS 10 RCE Hits Magento and Adobe Commerce

    A third maximum-severity, unauthenticated RCE has hit Magento and Adobe Commerce this year - but unlike StyleSmuggler, this one was patched before researchers published working exploits against it.

    BlockStrap (CVE-2026-103849): Another CVSS 10 RCE Hits Magento and Adobe Commerce

    BlockStrap, tracked as CVE-2026-103849, is the third maximum-severity (CVSS 10.0), unauthenticated remote code execution vulnerability to hit Magento and Adobe Commerce in 2026, after PolyShell in July and StyleSmuggler in September. There's a meaningful difference this time, though, and it's worth leading with: Adobe had already shipped the fix, in the routine October bulletin APSB26-153 on 13 October, before Sansec's research publicly named and detailed it two days later. If you applied that bulletin on schedule, you were already protected before this post, or the name "BlockStrap", existed.

    What it is

    • Mechanism: a "second-pass directive injection" in Magento's template engine. Sansec describes it as attacker-controlled data in a child template being signed and re-scanned at the root level of the rendering process, where a smuggled {{block}} directive can run during that second pass. It's a different specific flaw to StyleSmuggler, but a conceptually similar category of bug: Magento's template engine trusting content it shouldn't at a particular stage of rendering.
    • Authentication required: none.
    • Affected versions: Adobe Commerce and Magento Open Source up to and including 2.4.9, and Adobe Commerce B2B up to 1.5.3.

    Exploitation status

    As of Sansec's publication on 15 October, no active exploitation had been observed on live stores. That's a genuinely different situation to StyleSmuggler, where attackers were already inside stores before a patch existed. Here, researchers reproduced four distinct working attack routes within 24 hours of the patch becoming public, which tells you the bug is real and practically exploitable, but also that the sequence (patch, then public research, then proof-of-concept) worked the way responsible disclosure is supposed to. Adobe assigned it a Priority 2 rating with a 30-day patch window, a judgement call based on "no confirmed in-the-wild exploitation" rather than the CVSS score alone, worth noting given the score is identical to StyleSmuggler's.

    Two template-engine bugs in six weeks is a pattern worth naming

    We'd be doing our readers a disservice if we treated StyleSmuggler and BlockStrap as two unrelated, unlucky incidents. Both are rooted in how Magento's template rendering handles content it's told is safe at one stage and re-evaluates at another. That's not a coincidence worth shrugging off: it suggests the template engine's trust boundaries are an area Adobe (and the wider ecosystem) likely need to keep auditing, not just patch bug-by-bug as each variant surfaces. We dig into this pattern across the full year's advisories in our 2026 zero-day review.

    Recommended Actions

    1. Confirm APSB26-153 is applied. If it is, you're patched against this specific CVE already.
    2. If you haven't patched since 13 October, do it now, treating this the same as any other unauthenticated, maximum-severity RCE regardless of Adobe's 30-day Priority 2 window.
    3. Review whether custom code anywhere in your theme or extensions re-renders user- or merchant-supplied template content at more than one stage. Not a BlockStrap-specific fix, but exactly the kind of pattern this bug class exploits, and worth an audit if you have any custom templating logic of your own.

    Deploy's role

    This is a case where patching on schedule paid off directly. Every client on our support book had October's bulletin applied well before Sansec's research went public, which meant this one was simply a non-event for them rather than a scramble. That's been the throughline of our approach all year: Deploy has worked alongside a number of other leading Magento agencies through 2026's unusually heavy run of advisories, and it's exactly this kind of on-time, unglamorous patch discipline that's seen us recognised more than once this year, both by Sansec and within the wider community. If you want to make sure your store was covered by APSB26-153 before BlockStrap had a name, our support team can confirm it for you.

    Need Help with Your eCommerce Project?

    Get expert advice from our Magento specialists and marketing professionals.