Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-71362: Unauthenticated Customer Account Takeover in Adobe Commerce and Magento

Published Aug 11, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days7 mentions · peak 4 in a dayToday
CVSS9.1Critical · v3.1
EPSS91.7%100th percentile
CISA KEVYesAdded Sep 24, 2026
In the wildActivePer CISA KEV
Vendor
Adobe
IdentifiersCVE-2026-71362CWE-863 · Incorrect Authorization

CVE-2026-71362 is a critical incorrect authorization vulnerability affecting Adobe Commerce, Adobe Commerce B2B, and Magento Open Source. Improper handling of customer identity in account sessions allows attacker-controlled customer data retained during a failed account-edit operation to be copied back without sufficient filtering. An attacker-supplied customer identifier can overwrite the session's legitimate customer identity; subsequent validation checks that the customer exists without adequately verifying ownership. This enables customer-session switching and takeover of another customer's account. The vulnerability has a CVSS v3.1 score of 9.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N), requires no victim interaction, and has been exploited in the wild.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises customer-account confidentiality and integrity by allowing an attacker to impersonate another customer, access private account information, and perform actions available to that account. Exposed information can include personal details, order history, addresses, and stored payment tokens. The established impact is customer-account takeover and elevated access to sensitive resources, not administrator takeover or remote code execution. The CVSS assessment indicates high confidentiality and integrity impacts with no direct availability impact.

Mitigation

If you can’t patch tonight, do this now.

Until the fix is deployed, apply WAF rules targeting customer-identity manipulation and mass-assigned customer identifier parameters on account-edit and account-creation operations. Sansec Shield has blocked exploitation attempts. Restrict access to vulnerable customer-facing functionality where operationally feasible; administrative-panel restrictions alone do not address the customer-account attack surface. These controls reduce exposure but do not correct the authorization defect. Investigate anomalous customer-session activity and unauthorized account or configuration changes. If compromise is suspected, isolate the affected instance and rotate exposed credentials and API keys.

Remediation

Patch, then assume compromise.

Apply the vendor-designated fix for the installed product and supported release branch under Adobe security bulletin APSB26-92. For installations using Adobe's isolated-patch distribution, first install the latest required -p release for the supported branch, then apply the corresponding isolated patch. Alternatively, install a vendor-confirmed release incorporating the fix. Migrate unsupported installations to a supported branch. Exact affected and fixed version boundaries are inconsistent across the available information, so verify the applicable build and patch prerequisites against Adobe's product-specific guidance rather than assuming an August 2026 version label alone confirms remediation.

Public exploits

Exploits

2 exploits validated by Mallory's analysis.

View more in app →
cve-2026-71362-magento-atoThe repository contains four files: one standalone Python exploit, a detailed README, an MIT license, and a .gitignore excluding Python cache files and JSON output. Listed file sizes total 24,211 bytes; no repository URL, git reference, archive location, or archive size was supplied, so repository metadata is left unspecified with size_bytes set to 0. The stated attack requires one authenticated customer session. It allegedly submits an arbitrary customer id through a deliberately failing account-edit request, then loads the edit page to overwrite the session's customer identity. The tool is intended to iterate customer IDs, query GraphQL under each impersonated identity, and write a local customer-data dump. Documentation describes current/last-good/original session recovery, while the visible tail shows result accumulation, session-variable updates, a 0.3-second delay, statistics, and JSON serialization. Account creation through createCustomerV2 is suggested as a prerequisite option, not demonstrated in the visible implementation. Visible implementation details include subprocess-based curl transport, a PHPSESSID cookie, a fixed browser-like User-Agent, optional SOCKS5 hostname routing, and a hardcoded GraphQL extraction query. The query covers PII, addresses, order items and totals, payment methods, refunds, shipment tracking, wishlists, reviews, and stored payment-token metadata. Claims of complete database extraction are not established: orders and wishlist items have pageSize 50 limits, and no pagination is visible. No fixed external collection service or command-execution payload appears in the supplied code. Important limitations: exploit.py is truncated in the middle of its transport implementation, omitting the core poisoning, authentication verification, extraction parsing, and most control flow. Consequently, end-to-end functionality and the claimed identity transition cannot be verified. GraphQL cookie authentication and schema compatibility also require validation. The CVE assignment, CVSS 9.1 score, CISA KEV status, affected versions, and claimed fixes are repository assertions, not independently established facts; the bulletin and timeline contain placeholders such as APSB-2026-XX. The material is exploit-oriented rather than detection-only, but neither successful exploitation nor intentional fabrication can be concluded from this incomplete evidence.mahumadad · Disclosed Oct 23, 2026 · python · web · networkOperationalcve-2026-71362-magento-labThis repository is a self-contained Docker lab and working Python PoC for CVE-2026-71362, an incorrect authorization flaw in Adobe Commerce / Magento Open Source that allows customer-session identity switching and account takeover. The main exploit logic is in exploit/poc.py, which automates account registration, session poisoning via POST /customer/account/editPost with a malicious id field, and trigger/verification via GET /customer/account/edit and /customer/section/load. The exploit does not deliver code execution; instead, it abuses vulnerable session/customer object handling to overwrite the authenticated session's customer_id and impersonate arbitrary customers. Repository structure: exploit/poc.py contains the operational PoC; docker-compose.yml plus php/Dockerfile and php/entrypoint.sh build a disposable Magento environment with MariaDB, Redis, OpenSearch, PHP-FPM, and nginx; patch/Edit.vulnerable.php, patch/Edit.patched.php, and patch/official-APSB26-92-module-customer.patch document and toggle the vulnerable/fixed controller implementation; scripts/patch.sh and scripts/unpatch.sh provide A/B testing of the fix; docs/ROOTCAUSE.md explains the vulnerable code path and docs/DETECTION.md provides detection/WAF guidance. Exploit capability: the PoC registers an attacker account, optionally creates a victim account for demonstration, then iterates customer IDs or targets a specific victim ID. For each target, it submits a deliberately failing editPost request carrying id=<victim_id>, causing attacker-controlled customer_form_data to persist in session. A subsequent GET to /customer/account/edit causes Magento's vulnerable populateWithArray() flow to copy id onto the customer object and Session::setCustomerData() to overwrite session customer_id. The script then reads victim identity/PII from account pages and AJAX customer section data. This is a real exploit, not merely detection, and is operational but basic/hardcoded rather than framework-weaponized.dinosn · Disclosed Aug 15, 2026 · python · bash · web · networkPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AdobeCommerceapplication
AdobeCommerce B2bapplication
AdobeMagentoapplication
FAQ

Frequently asked questions

Is CVE-2026-71362 exploited in the wild?
Yes. As of Nov 17, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Sep 24, 2026.
Is there a public exploit for CVE-2026-71362?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2026-71362, the earliest disclosed Aug 15, 2026.
Is there a patch for CVE-2026-71362?
Apply the vendor-designated fix for the installed product and supported release branch under Adobe security bulletin APSB26-92. For installations using Adobe's isolated-patch distribution, first install the latest required -p release for the supported branch, then apply the corresponding isolated patch.
What products are affected by CVE-2026-71362?
Adobe Commerce, Adobe Commerce B2b, and Adobe Magento.
How severe is CVE-2026-71362?
CVE-2026-71362 has a CVSS v3.1 score of 9.1 (Critical) and an EPSS score of 91.7% (100th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

111 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+24 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity76Community discussion across Reddit, Mastodon, and other social sources.