PolyShell Hits the KEV List: The Adobe Commerce and Magento Upload Flaw Sansec Says Has Already Breached Hundreds of Stores

PolyShell Hits the KEV List: The Adobe Commerce and Magento Upload Flaw Sansec Says Has Already Breached Hundreds of Stores

PolyShell Hits the KEV List: The Adobe Commerce and Magento Upload Flaw Sansec Says Has Already Breached Hundreds of Stores

CISA added CVE-2026-48356, the Adobe Commerce and Magento file-upload vulnerability known as PolyShell, to its Known Exploited Vulnerabilities catalog on October 27, citing evidence of active exploitation, with federal agencies given until November 10 to remediate. Rated 9.3 (critical), the flaw is an unrestricted upload of a file with a dangerous type: an unauthenticated attacker can push an executable file onto any affected store and, depending on the web server configuration, achieve arbitrary code execution in the context of the current user — or stored XSS and account takeover where direct execution is blocked. Adobe's bulletin APSB26-73 is the vendor fix referenced by CISA's entry.

PolyShell is not a new discovery — it is a long-standing flaw that finally caught up with the patch gap. Sansec, the e-commerce forensics team that found and named it, disclosed the bug on March 17, 2026: the vulnerability sits in Magento's REST API and lets attackers upload files disguised as images — a polyglot that passes validation as an ordinary picture. Sansec reported observing attacks against 79.5% of all stores at disclosure time, and noted the vulnerable code has existed since the very first Magento 2 release. Adobe shipped the fix in Magento 2.4.9 in May (originally landed in the 2.4.9 pre-release branch under APSB25-94), but at the time the fix was not backported to the supported production lines 2.4.8, 2.4.7, and earlier — leaving most of the installed base on stores that could be written to, without an isolated patch to install.

Whether the upload becomes RCE depends on the web tier. Sansec's breakdown: stock nginx 2.0.0 through 2.2.x is exploitable through the index.php filename trick; any store running a non-stock nginx configuration that passes all .php files to fastcgi is exploitable at any version; and Apache before 2.3.5 without php_flag engine 0 in upload locations likewise executes the payload. In less favorable configurations the uploaded file still persists on disk — a latent problem that one future configuration change can turn active.

The October development that pushed this onto KEV: Sansec says it has now watched attackers use PolyShell to breach hundreds of e-commerce stores, injecting a malicious loader through a Magento CMS block. The loader fetches and executes an attacker-controlled payload; no next-stage malware has been recovered yet, so the campaign's end goal is still unclear — but the activity is assessed as ongoing since at least July 2025. The platform has now absorbed two critical upload-and-execute stories this year — StyleSmuggler's zero-day RCE in September and PolyShell's KEV listing now — and the message to merchants is that unattended storefronts are being worked at scale.

What Should You Do?

  1. Get onto a fixed release immediately — upgrade to Magento/Adobe Commerce 2.4.9 or later and apply APSB26-73; the KEV listing makes this a deadline, not a suggestion, even for non-federal merchants.
  2. Close the execution path in your web server config — disable PHP execution in upload and static content directories (nginx: deny .php in upload locations; Apache: php_flag engine 0), so a polyglot that slips through validation cannot run.
  3. Scan the upload directory for polyglot files — look for images containing embedded script and unexpected recent files; an uploaded-but-unexecuted payload is still a foothold on disk.
  4. Watch the REST API for abuse — unauthenticated file writes through REST endpoints are the entry path; log and alert on anomalous upload traffic rather than assuming the storefront's front door is the only one.

The WAF Angle

PolyShell is a reminder that upload validation is where web application firewalls earn their keep — and where they get gamed. A polyglot file reads as an image to extension checks, MIME sniffing, and most signature rules; the malicious half of the payload hides inside bytes that a naive Content-Type check happily waves through. A WAF that inspects upload endpoints for executable content signatures, rather than stopping at file extensions, closes the gap that Magento's own REST API left open — and the execution-layer hardening above is the defense that still works when a crafted file lands anyway. It joins a familiar lineage on this site: Pillow's Ghostscript filename injection showed the same image-payload pattern server-side, and the store infection wave echoes the mass-exploitation operators we have tracked all month. For e-commerce specifically, patch velocity on the platform plus upload-path rules at the edge is the pairing that actually stops this class.

Sources