On 27 October 2026, CISA confirmed PolyShell (CVE-2026-48356) is being actively exploited by adding it to its Known Exploited Vulnerabilities catalogue. Here's why that matters even if you're not a US federal supplier.

On 27 October 2026, the US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-48356 (the Magento and Adobe Commerce flaw we covered back in July as PolyShell) to its Known Exploited Vulnerabilities (KEV) catalogue. That's a formal confirmation from a government agency that this vulnerability is being actively used in real attacks, not just a theoretical risk. If you sell to US federal agencies or their suppliers, this is a compliance deadline. If you don't, it's still worth reading, and here's why.
CISA's KEV catalogue is a running list of vulnerabilities confirmed to be under active exploitation. Under Binding Operational Directive 26-04, US federal civilian agencies are legally required to remediate any KEV-listed vulnerability in their own systems within a set window. For this entry, CISA set a 14-day deadline of 10 November 2026, a notably tight window that reflects how long PolyShell had already had a fix available (since July) with little excuse for federal systems still running vulnerable code. If you want to check the window for any other entry, the live CISA KEV catalogue is the authoritative source rather than secondary coverage, including ours.
Worth knowing: this isn't the only Magento CVE on the 2026 KEV list. CVE-2026-75650 (StyleSmuggler) was added back on 8 September 2026 (a day after Adobe's emergency hotfix) with a far tighter three-day federal deadline, reflecting that it was exploited before any patch existed at all. CVE-2026-103849 (BlockStrap) has not, as of this writing, been added to KEV.
KEV status isn't just a government filing requirement. In practice, it's become a reference point well beyond federal agencies:
In other words: even if nobody is legally obligated to patch on CISA's timeline, "this CVE is on the KEV list" is becoming a shorthand that risk teams outside government actually use.
Unlike some of the other advisories we've covered this year, there's no new patch to chase here. PolyShell has had an isolated fix available since 14 July 2026 (APSB26-73). The action item today isn't "wait for Adobe", it's "go verify you actually applied the July patch", which is a meaningfully easier task. If you're not sure, the indicators of compromise and file-upload checks in our original PolyShell write-up are still the right place to start.
We flagged and patched APSB26-73 for every affected client back in July, well ahead of today's KEV listing. That meant this news was simply a confirmation exercise for our support clients rather than a fire drill. That's been the pattern all year: Deploy has stayed close to Sansec's research and Adobe's bulletins throughout 2026's unusually busy run of Magento advisories, work recognised more than once this year both by Sansec and within the wider agency community. We've pulled the whole year's pattern together, PolyShell included, in our full 2026 security review. If you need a second opinion on whether every store in your portfolio is actually covered, our team can check.