Back to Blog Homepage
    Deploy Blog
    Nathan Chick

    August 2026 Adobe Commerce Patch (APSB26-92): Five Critical, Zero-Login Flaws

    Adobe's August bulletin fixed seven vulnerabilities in Adobe Commerce and Magento Open Source, five of them critical and exploitable with no login at all. It landed the same day 2.4.6 lost standard support.

    August 2026 Adobe Commerce Patch (APSB26-92): Five Critical, Zero-Login Flaws

    Adobe has released APSB26-92, its regular monthly security bulletin for Adobe Commerce and Magento Open Source, fixing seven vulnerabilities, five of them rated Critical. Adobe's bulletin rates it Priority 2, meaning no active exploitation has been confirmed yet, but three of the five critical issues need no login at all, so we wouldn't read "Priority 2" as "take your time."

    What's fixed

    CVE Type CVSS Severity Auth required
    CVE-2026-71362 Incorrect Authorization 9.1 Critical No
    CVE-2026-48414 Stored XSS 7.7 Critical Yes
    CVE-2026-48413 Stored XSS 8.7 Critical Yes
    CVE-2026-48415 Incorrect Authorization 7.6 Critical Yes
    CVE-2026-48416 Incorrect Authorization 7.5 Critical No
    CVE-2026-48411 Incorrect Authorization 6.8 Important Yes
    CVE-2026-48412 Incorrect Authorization 2.7 Moderate Yes

    The headline issue is CVE-2026-71362, an incorrect-authorisation flaw (CWE-863) that leads to privilege escalation and, unlike most of the rest of the batch, requires no authentication to trigger. The stored XSS pair (CVE-2026-48414 and -48413) can escalate to arbitrary code execution once an attacker is authenticated, which is the usual pattern: get a foothold via a low-privilege account, then use the XSS to climb.

    Affected Versions

    • Adobe Commerce: 2.4.4 through 2.4.9 (any release through July 2026)
    • Adobe Commerce B2B: 1.3.3 through 1.5.3
    • Magento Open Source: 2.4.6 through 2.4.9
    • Fixed versions were published in Adobe's August 2026 release line for all three products.

    The 2.4.6 coincidence

    This bulletin landed on the same day Magento 2.4.6 reached the end of its standard support window. If you're still on 2.4.6, you'll keep getting security-only fixes like this one until May 2028, but you've lost everything else: no new features, no non-security bug fixes, and historically those security-only backports arrive later than the fixes for currently-supported lines. We've written separately about what 2.4.6 end-of-support actually means for your store if you want the full picture.

    Recommended Actions

    1. Patch all seven, but if you need to stage testing, prioritise CVE-2026-71362 and CVE-2026-48416 first, the two that need no authentication at all.
    2. Test custom and third-party modules against the authorisation changes specifically; incorrect-authorisation fixes occasionally tighten ACL checks in ways that catch custom admin extensions off guard.
    3. If you're on 2.4.6, treat this as a prompt to start planning your upgrade rather than settling into security-only mode for the next two years.

    This was the first of what turned into an unusually busy run of Magento security bulletins through autumn 2026. We've pulled the whole year's pattern together, including StyleSmuggler and BlockStrap, in our full-year review of 2026's Magento zero-days. As ever, Deploy's support clients had this patched and tested in staging within 24 hours of release. If you'd rather hand patch management to someone watching the bulletins full-time, that's exactly what our fixed-fee support model is for.

    Need Help with Your eCommerce Project?

    Get expert advice from our Magento specialists and marketing professionals.