CVE-2026-48356
🔴 High In CISA KEVAdobe Commerce, Adobe Commerce B2B, Magento Open Source, and Adobe Commerce Events. Sansec tracks this as "PolyShell" · Commerce ≤ 2.4.9 / 2.4.8-p5 / 2.4.7-p10 / 2.4.6-p15 / 2.4.5-p17 / 2.4.4-p18 ; B2B ≤ 1.5.3 / 1.5.2-p5 / 1.4.2-p10 / 1.3.4-p17 / 1.3.3-p18 ; Magento Open Source ≤ 2.4.9 / 2.4.8-p5 / 2.4.7-p10 / 2.4.6-p15 ; Commerce Events ≤ 1.20.0
99.30th percentile
due 2026-11-10
Exploitation
accesson.php. A later Sansec study (24/10/2026) found a CMS-block loader on 953 stores since July 2025 and, of 169 loader-infected installs missing at least one core patch, 102 (60%) also had files uploaded through PolyShell or SessionReaper, against a 32% baseline across 3,024 comparable installs — a data-backed correlation with CVE-2025-54236, though no source claims a single campaign or names an actor. No public PoC was found. Two record problems: the SSVC block moved from exploitation none to active without its own timestamp being bumped (still 14/07/2026), and the kev block is still absent despite the KEV listing, so the record alone understates this badly. The identification of this CVE with PolyShell rests on Sansec, and note that the CVE was published 14/07/2026, four months after the attacks began Update 29/10/2026: PoC code is now circulating — two exploit-aggregator entries published 27/10/2026 pointing at a GitHub repository, with a machine-estimated confidence score rather than a verified run, the reporting account not the repository owner and a minimal README. Log it as code in circulation, not a verified working exploit. The kev block is still absent from the record. The PolyShell identification remains Sansec's alone, which a second vendor confirmed explicitly on 28/10: Adobe's bulletin and the CISA entry do not use the name, and NVD merely links Sansec.Timeline
- 14/07/2026CVE record published (CVE List)
- 27/10/2026953 online stores infected with scanner-evading JavaScript skimmer
- 27/10/2026Added to the CISA KEV catalogue
- 28/10/2026Magento/Adobe Commerce JS-injection campaign hits 953 online stores — PolyShell now in CISA's KEV catalog
- 29/10/2026Brotli decoder flaw and Adobe Commerce "PolyShell" added to CISA KEV
- 10/11/2026CISA deadline for US federal agencies
Risk
Fix
2.4.9-2026-jul and the matching -2026-jul builds, Adobe APSB26-73, 14/07/2026) ; Commerce Events 1.21.0. The fix first landed in 2.4.9 on 12/05/2026 and was not backported until 14/07, so anything on 2.4.8 or earlier was exposed for four months. Patching is not enough. Deploy a WAF rule blocking the vulnerable API calls, which Sansec calls the only control that stops the attack itself. Restrict web access to pub/media/custom_options/ (on nginx the rule must precede any PHP location block ; on Apache use the .htaccess that disables the PHP engine). Remove uploaded files even where execution is blocked, because they become exploitable again after a configuration change, migration or web server swap. Hunt for any .php, .phtml or .phar in pub/media/custom_options/, for accesson.php outside the upload directory, and for CMS pages or static blocks referencing lanhd6549tdhse[.]top, jslibrary[.]net or canevaslab[.]comOfficial description
Adobe Commerce is affected by an Unrestricted Upload of File with Dangerous Type vulnerability that could result in arbitrary code execution in the context of the current user, potentially gaining elevated access or control over the victim's account or session. Exploitation of this issue requires user interaction in that a victim must visit a maliciously crafted URL or interact with a compromised web page. Scope is changed.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
CWE-434