On this page
CVE-2026-71362 is an unauthenticated authorization flaw in Adobe Commerce and Magento that CISA added to its Known Exploited Vulnerabilities (KEV) catalog on 24 September 2026. Adobe fixed it on 11 August in bulletin APSB26-92. The action is to confirm, on the server, that the August 2026 security patch is applied. A version number alone will not show it.
| Fact | Detail | Source |
|---|---|---|
| CVE id | CVE-2026-71362, incorrect authorization (CWE-863), privilege escalation | Adobe APSB26-92, NVD |
| Severity | CVSS 3.1 base score 9.1, network, no privileges, no user interaction; Adobe priority 2 | Adobe APSB26-92 |
| Bulletin date | 11 August 2026; page last updated 18 August 2026 | Adobe APSB26-92 |
| Affected | Adobe Commerce 2.4.4 to 2.4.9, Commerce B2B 1.3.3 to 1.5.3, Magento Open Source 2.4.6 to 2.4.9, all at the July 2026 level or earlier | Adobe APSB26-92 |
| KEV | Added 24 September 2026, due 27 September 2026, forensic triage flagged | CISA catalog, KEV data |
| Exploitation | Confirmed by CISA's listing; evidence not published. Adobe's bulletin still said "not aware" at our check | CISA; Adobe |
| Checked | 2 November 2026 | this page |
What does this flaw let an attacker do?
Sansec describes it as an unauthenticated customer account takeover: a request can switch a customer session to another customer's account, with no existing account, admin rights or user interaction. Adobe classes it as privilege escalation and rates it Critical, the highest of seven CVEs in that bulletin.
For a shop, the exposure is customer data and customer-account actions: order history, saved addresses and whatever else a logged-in customer can see or change. It is not a server takeover on its own. That is the difference from StyleSmuggler, the September remote code execution bug in the same product, which needs a different fix and a key rotation.
We do not reproduce how the flaw is triggered, and you do not need it to check your store.
Why are there three KEV entries on Adobe Commerce?
CISA's catalog now carries three Adobe Commerce entries added in under two months. CVE-2026-75650 went in on 8 September and CVE-2026-71362 on 24 September, per the KEV data. On 27 October CISA added CVE-2026-48356, a CVSS 9.6 dangerous file upload flaw that Adobe fixed in its July bulletin APSB26-73, with a federal due date of 10 November. Stores on the July 2026 builds or later have that fix; anything older is open to all three. They are unrelated bugs with different fixes, and the PHP runtime flaw in what PHP2Shell means for Magento stores is a different matter again.
Which builds are affected and which are fixed?
Adobe's bulletin names every build at the July 2026 level or earlier as affected. The fixed builds carry the August suffix, as listed in Adobe's CVE record at NVD.
| Product | Affected (July 2026 level or earlier) | August 2026 builds in the CVE record |
|---|---|---|
| Adobe Commerce | 2.4.4 to 2.4.9 | 2.4.9, 2.4.8, 2.4.7, 2.4.6, 2.4.5, 2.4.4, each with -2026-aug |
| Adobe Commerce B2B | 1.3.3 to 1.5.3 | 1.5.3, 1.5.2, 1.4.2, 1.3.4, 1.3.3, each with -2026-aug |
| Magento Open Source | 2.4.6 to 2.4.9 | 2.4.9, 2.4.8, 2.4.7, 2.4.6, each with -2026-aug |
The NVD record for Adobe Commerce lists the 2.4.8 to 2.4.4 August builds in both its affected and unaffected ranges at our 24 October check. That looks like a data quirk in the record. Use Adobe's bulletin and your own patch status, not that overlap.
Adobe's later bulletins APSB26-138 (8 September) and APSB26-153 (13 October) list "August 2026 and earlier" and "September 2026 and earlier" as affected for their own CVEs. Neither restates CVE-2026-71362. Do not assume a September or October build includes the August fix. Confirm it.
Why can a store think it is patched and not be?
Three things cause the gap.
- The fix ships as an isolated patch. Per Sansec, APSB26-92 came as isolated patch files, not a new Composer release, and required the latest -p release for your line first. The version in your admin panel can stay the same after applying it.
- The hotfix is a different item. Adobe's September and October bulletins say to apply the CVE-2026-75650 hotfix in addition to the monthly update. A team that rushed that hotfix on 8 September may believe the store is current. MagentoInfo argues a store that took only the hotfix on a July base is still open to this flaw. That reading is the site's, not Adobe's, but it is the right thing to rule out.
- Adobe's page says "no exploits". The bulletin was last updated on 18 August. Its exploitation line predates the CISA listing, so a reader who relies on it reads the risk as lower than it is.
How do I check the August patch is really on?
If a host or agency manages the store
Send this and keep the reply:
For [your store], is the August 2026 security update from Adobe bulletin APSB26-92 (CVE-2026-71362) applied on every Adobe Commerce, B2B or Open Source component? Please send the patch status output with the date, say which build the store runs now, and confirm the CVE-2026-75650 hotfix, the July update from APSB26-73 (CVE-2026-48356, in KEV since 27 October) and the October update from APSB26-153 are applied separately. Has anyone reviewed customer-account activity since 24 September?
- Get the patch status output, dated, in writing
- Get the current build, including the month suffix
- Get the separate status of the StyleSmuggler hotfix
- Ask who reviewed customer-account activity, and for which dates
If you run the server yourself
Adobe's Quality Patches Tool reports each patch as Applied, Not applied or N/A. The base command is ./vendor/bin/magento-patches status. MagentoInfo suggests filtering it with vendor/bin/magento-patches -n status | grep -E "2026-08|Status" and reading any August file that is not Applied as an open store.
- Run the status command in the project root, once per Commerce, B2B and Open Source component you have
- Look for the August 2026 security files and a status of Applied
- Treat "Not applied" and "N/A" as unresolved, and find out why before you stop
- Apply the latest -p release for your line first if the isolated patch will not install
- Apply the CVE-2026-75650 hotfix and the October update as their own steps
- Save the output with the date, and the build, in the ticket
Adobe's tool page does not describe security patches as a separate category. If the August files do not appear in your status output, ask your agency or Adobe support how to show proof, rather than guessing from the version. If your line is close to the end of support, which Adobe Commerce versions still get patches is worth checking before you plan the upgrade.
Am I affected? Where you stand right now
A check from outside can sometimes read a Magento version. It cannot see an isolated patch, so it cannot tell whether the August update is installed.
- Detected Your store serves Magento or Adobe Commerce and the version is in the affected ranges above. Treat the store as exposed. Apply the August update (and the later ones) now, then review customer-account activity.
- Unknown The version is hidden, or it looks current but nobody has shown the August patch status. This is the common case. Get the status output from the server or your agency.
- Confirmed by owner evidence You hold dated patch status output showing the August 2026 files Applied for each component. The patch state is confirmed. Whether any account was taken over before that date is a separate question.
No scan, ours included, moves you from "unknown" to "confirmed".
Was a customer account taken over before the patch?
Possibly. Adobe's bulletin says it knew of no exploits, and the CISA listing says otherwise. CISA does not publish its evidence, so we do not know how many stores were touched and we name none. The KEV entry flags forensic triage in its required action, and lists known ransomware use as unknown.
The CISA due date of 27 September comes from BOD 26-04, which binds federal civilian agencies only. It tells a private shop how urgent CISA considers the bug. It is not a legal deadline for you.
Practical checks for a store that was unpatched after 11 August (our suggestions, not Adobe's):
- Customer accounts whose email, password or address changed without a matching customer request.
- Logins or orders for one account from unrelated IP addresses in a short window.
- Customer support messages about orders or saved details that the customer did not change.
- Access logs for unusual session behavior around account pages, if your host keeps them.
If you find signs of entry, patch first, then ask your host what logs exist and what your data-protection duties are. While the store is under review, how to find a Magento checkout skimmer is a sensible second check, and the wider Magento hardening checklist covers what to fix afterwards.
Where does Red fit?
The free scan identifies the technologies your site serves and matches each version to known vulnerabilities. It is a lookup: it can say a version is affected, not whether your setup is exposed or whether the August patch is installed. For why a lookup cannot settle patch state, read the limits of an outside scan and ways to confirm a fix landed. The full scan is $100 and sends an AI red team at what is reachable from outside.
If an agency runs the store, this guide to patching responsibility sets out what to ask. The wider picture for shops is in the other ecommerce guides, the October 2026 ecommerce roundup and the tracker.
Questions people ask
Is CVE-2026-71362 actually being exploited?
CISA added it to the Known Exploited Vulnerabilities catalog on 24 September 2026, which CISA does on evidence of active exploitation. CISA does not publish that evidence, and Adobe's bulletin, last updated 18 August, still says it knew of no exploits. Treat the CISA entry as the later and stronger signal.
I applied Adobe's hotfix for the September zero-day. Does that cover this one?
No. The hotfix for CVE-2026-75650 and the August security update for CVE-2026-71362 are separate items, and Adobe's September and October bulletins tell you to apply the hotfix in addition to the monthly update. Having one tells you nothing about the other. Check the August patch by itself.
How do I check the August patch is installed on Adobe Commerce?
On the server, run the Quality Patches Tool status command and look for the August 2026 security files marked Applied for each installed component. Ask your host or agency for that output with a date. The version number shown in the admin panel is not enough on its own.
Can an online scanner tell me whether my store has the August patch?
No. A scan from outside can sometimes read a Magento version, but an isolated patch does not change what the storefront shows. Only the server, or whoever manages it, can show which patch files are applied.
I patched late. Was a customer account already taken over?
It is possible if the store was reachable and unpatched after 24 September at the latest, and CISA's entry flags forensic triage. Patching closes the hole and does not tell you what happened before. Review customer-account changes and access logs for the period, and ask your host for what they hold.
Do I need to do anything if I run Magento Open Source?
Yes, if you run 2.4.6 to 2.4.9 at the July 2026 level or earlier. Adobe's bulletin lists Magento Open Source in scope with its own August builds. Open Source 2.4.4 and 2.4.5 are not named in the bulletin, so ask Adobe's documentation or your agency before assuming either way.
Sources
- Adobe security bulletin APSB26-92 (Adobe Commerce and Magento Open Source, 11 August 2026)CVE-2026-71362, CVSS 9.1, priority 2, affected builds. The page shows a last update of 18 August 2026 and still says Adobe is not aware of exploits. Checked 2 November 2026.
- NVD: CVE-2026-71362Adobe's CVE record with the affected and unaffected build lists, CWE-863 and the CISA KEV fields. Record modified 25 September 2026.
- CISA Known Exploited Vulnerabilities catalogEntry for CVE-2026-71362: added 24 September 2026, due 27 September 2026.
- CISA KEV data (cisagov/kev-data, CSV)Machine-readable catalog. Gives the required action, the forensic triage flag and the unknown ransomware field. Read 2 November 2026.
- CISA BOD 26-04: Prioritizing Security Updates Based on RiskThe directive behind the KEV due date. It binds federal civilian agencies only.
- Sansec: Adobe patches critical Magento account takeover (APSB26-92), 11 August 2026Describes the flaw as an unauthenticated customer account takeover, the isolated-patch format and the -p prerequisite.
- Adobe security bulletin APSB26-73 (Adobe Commerce and Magento Open Source, 14 July 2026)The July update that fixes CVE-2026-48356, added to KEV on 27 October 2026. Still says Adobe is not aware of exploits. Checked 2 November 2026.
- Adobe security bulletin APSB26-138 (Adobe Commerce and Magento Open Source, 8 September 2026)The September monthly update. Lists the earlier hotfix as required in addition.
- Adobe security bulletin APSB26-146 (StyleSmuggler hotfix, 7 September 2026)The separate, earlier KEV entry. Its hotfix is a different item from the August patch.
- Adobe security bulletin APSB26-153 (Adobe Commerce, 13 October 2026)The October update. It does not mention APSB26-92.
- Adobe Quality Patches Tool: usage and status commandHow magento-patches status reports Applied, Not applied and N/A. Checked 24 October 2026.
- MagentoInfo: CVE-2026-71362 and Adobe Commerce exploitationSecondary source, used only for the grep form of the status command and the hotfix-on-an-old-base reading. Not an Adobe or CISA statement.
Facts on this page are dated and point at the primary source next to them. If a vendor status changes after the date shown, the vendor's page wins; tell us at support@run.cloud and we will update it.