Indicators and notes for PolyShell (CVE-2026-48356), the Magento and Adobe Commerce file-upload flaw, with credit to the researchers. Not tested, no warranty.
Read first. This package is aggregated from a public research article by SOC-Lite by BansalAI. It is not tested by us, it comes with no warranty, and it is not professional advice. It is as of 2026-10-28 and will go stale. See DISCLAIMER.md. We are not affiliated with Sansec or any other source credited in CREDITS.md, and none of them reviewed or endorsed this package.
On 2026-10-27 the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-48356, nicknamed PolyShell, to its Known Exploited Vulnerabilities catalog. The flaw is in Adobe Commerce and Magento Open Source, the software behind some online stores. The security firm Sansec published a report on it on 2026-03-17 (and has updated it since). The report says a visitor with no login can upload a file through the store's shopping cart, and that the file can then be run on many stores. It also lists indicators of attacks that Sansec saw.
This repository copies those indicators (with credit) and adds a short guide to checking your own store for them.
Not technical? Start with the plain-language version: Online Store on Adobe Commerce or Magento? Ask About This Flaw on the SOC-Lite blog. It gives four questions to put to whoever runs your store.
| File | What |
|---|---|
iocs/iocs.csv | One row per indicator, with the source, the date, how fragile it is, and a review date |
docs/hunt-guide.md | What to check on a store's server, logs and page content, what the results do and do not mean, and what to do if something looks real |
CREDITS.md | The research this is built from, and what we took from it |
DISCLAIMER.md | The full disclaimer |
index.php, test.php).
They matter when they sit where they should not, such as the store's upload folder. The rows say which.iocs.csv| Column | Meaning |
|---|---|
id | Stable row ID (PS-nnnn) |
wave | Always polyshell in this release |
type | ip, domain, file-path, filename, string or behaviour |
value | The indicator. Addresses and domains are written as normal text, not defanged. Never open them in a browser |
match | exact, prefix or wildcard |
evidence | Where it would show: network, file, response-body or access-log |
fragile | yes if the attacker can change it trivially |
verified | yes only when two independent primary sources report it. no means a single source |
source_url, source_date | Where we took it from and the date of that source |
fetched, review_by | When we read it, and when it should be re-checked. Addresses and domains have short review dates |
notes | Context and caveats. Sentences starting "Our note" are ours, not Sansec's |
Search your own store with the steps in the hunt guide. This package does not ship anything that runs on your systems or collects data from them.
The text we wrote is licensed under CC BY 4.0 (LICENSE). The indicator values and facts belong to the researchers who reported them: they are credited in CREDITS.md, and we do not relicense them. Details and how to credit us are in NOTICE.md.
Sansec's report is the source for everything here and may be updated. For its complete text, including the technical detail we leave out, follow the link in CREDITS.md. For the fix itself, read Adobe's security bulletin and support article, linked there too.
If something looks real, preserve the logs first, take the store out of service if you can, and call whoever runs it for you. SOC-Lite by BansalAI helps small and mid-sized Central Florida businesses review alerts and work with their IT person or MSP. Book a free 20-minute visibility check. More plain-language security write-ups are on the SOC-Lite blog.