Back to Blog Homepage
    Deploy Blog
    Nathan Chick

    Adobe Commerce October 2026 Security Round-Up: APSB26-153 Explained

    Adobe's 13 October bulletin fixed 11 vulnerabilities, including a CVSS 10 flaw patched before researchers even named it. Here's what's in APSB26-153 and the order to apply your patches in.

    Adobe Commerce October 2026 Security Round-Up: APSB26-153 Explained

    Adobe's October security bulletin, APSB26-153, fixes 11 vulnerabilities across Adobe Commerce, Adobe Commerce B2B and Magento Open Source. One of them, CVE-2026-103849, turned out to be a genuinely good news story for once: Adobe shipped the fix here, in this routine bulletin, before Sansec published the research that would later name and detail it as BlockStrap. We'll come back to why that sequencing matters. Adobe rates this bulletin Priority 2.

    What's fixed

    CVE CVSS Type Impact
    CVE-2026-103849 10.0 Template engine input neutralization Arbitrary code execution
    CVE-2026-92909 9.8 Incorrect authorization (B2B) Arbitrary code execution
    CVE-2026-91013 9.3 Stored XSS Privilege escalation
    CVE-2026-100133 9.3 Stored XSS Privilege escalation
    CVE-2026-92464 9.1 Improper input validation Arbitrary code execution
    CVE-2026-92911 8.7 Stored XSS Arbitrary code execution
    CVE-2026-95631 8.7 Improper input validation Arbitrary file system write
    CVE-2026-92908 8.3 Incorrect authorization (B2B) Security feature bypass
    CVE-2026-92922 8.1 Stored XSS Privilege escalation
    CVE-2026-92910 7.2 Incorrect authorization (B2B) Security feature bypass
    CVE-2026-95630 4.3 Improper input validation Security feature bypass

    Three of these (CVE-2026-92909, -92908 and -92910) specifically affect Adobe Commerce B2B's authorisation model, worth a closer look if you run a B2B storefront with company accounts or quote workflows, since incorrect-authorisation bugs there tend to mean one company account can see or act on another's data.

    Affected Versions

    • Adobe Commerce: 2.4.4 through 2.4.9 (September 2026 releases and earlier)
    • Magento Open Source: 2.4.6 through 2.4.9
    • Adobe Commerce B2B: 1.3.3 through 1.5.3

    This is separate from the StyleSmuggler hotfix

    Worth saying plainly, because it trips people up every cycle: APSB26-153 does not include or replace September's emergency hotfix for StyleSmuggler (CVE-2026-75650), APSB26-146. Adobe's own guidance is to apply both: the October bulletin on its normal schedule, and the September hotfix separately if you haven't already. If you've been meaning to "catch up properly" on Magento patches, this month is as good a prompt as any to confirm both are actually live.

    Patch order and testing

    1. Confirm the September StyleSmuggler hotfix is already applied before anything else. It's the older, higher-urgency item.
    2. Apply the full October bulletin as one unit.
    3. Test B2B authorisation flows specifically if you run Adobe Commerce B2B, given three of the eleven CVEs sit in that layer.
    4. Check any WYSIWYG-dependent CMS content if you've recently moved to 2.4.9 and the TinyMCE-to-HugeRTE switch. Not directly related to this bulletin, but a sensible moment to tick that box while you're already in a patch-and-test cycle. We cover that separately in our HugeRTE audit guide.

    Why the BlockStrap timing is actually reassuring

    Compare this to September: StyleSmuggler was exploited in the wild for three days before any fix existed. This time, Adobe fixed CVE-2026-103849 in this routine bulletin on 13 October, and it was only two days later, on 15 October, that Sansec's own research named it BlockStrap and reproduced working exploits against it. In other words, this is one instance in an otherwise rough year where the patch came first and the public proof-of-concept came after, exactly how responsible disclosure is supposed to work. We go into that case in more depth in our BlockStrap post.

    Deploy's role

    This was the fourth Adobe security bulletin of the year we've applied to our full client book within 24 hours of release, after August's APSB26-92, September's APSB26-146 and September's APSB26-138. It's been a demanding year for anyone keeping a Magento store patched, and Deploy has stayed at the centre of it alongside a number of other leading agencies, work that's been recognised more than once this year, both by Sansec and within the wider community. We've gathered the full pattern of 2026's advisories, including what we think it actually means for how merchants should defend themselves, in our full-year review. If you'd like this handled for you on every release going forward, our fixed-fee support model is built for exactly this cadence.

    Need Help with Your eCommerce Project?

    Get expert advice from our Magento specialists and marketing professionals.