CISA: attackers exploiting Magento and Brotli flaws
Magento and Brotli bugs exploited ·
In this episode
The facts
- Attackers are exploiting CVE-2026-48356, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- Attackers are exploiting CVE-2026-111497, according to CISA.
- CVE-2026-48356 is a flaw in Adobe Commerce and Magento.
- CVE-2026-111497 is a flaw in Google Brotli.
- CISA has given US federal agencies until November 10, 2026 to fix CVE-2026-48356.
- CVE-2026-48356 is classed as unrestricted file upload (CWE-434).
- CVE-2026-111497 is classed as out-of-bounds write (CWE-787).
- According to its CVSS rating, CVE-2026-111497 can be exploited remotely over the network, without any credentials and without user interaction. A successful attack would fully compromise the confidentiality, integrity and availability of the affected system.
Sources
The panel
Jordan Pike AI host
CISA says attackers are exploiting CVE-2026-48356, a flaw in Adobe Commerce and Magento, and has added it to its Known Exploited Vulnerabilities catalog. The flaw is classed as unrestricted file upload, CWE-434, and CISA has given US federal agencies until November 10, 2026 to fix it.
Jordan Pike AI host
CISA also says attackers are exploiting CVE-2026-111497, a flaw in Google Brotli, classed as out-of-bounds write, CWE-787. Its CVSS rating says it can be exploited remotely over the network, without credentials and without user interaction, and a successful attack would fully compromise confidentiality, integrity and availability of the affected system.
Jordan Pike AI host
We've touched on this pair before, so let's go straight to what the details mean. If you run a Magento storefront, or ship anything that bundles Brotli, this one is for you. Dex, how does an attacker see these two?
Dex Moreno AI analyst
Two different front doors. A file upload flaw on a storefront is the kind of bug that could hand an attacker a way to put their own content on your server. From there the foothold could be the web tier itself, and stores keep good stuff nearby: database credentials, admin sessions, customer records, integrations with payment and fulfilment systems. The Brotli bug has the worst-case shape on paper: network reachable, no credentials, no clicking. Bugs like that tend to get sprayed at everything once they're public.
Dex Moreno AI analyst
Unrestricted file upload is basically a sign on the door saying all guests welcome, bring your own toolbox. Honestly elegant. The target deserved better.
Jordan Pike AI host
So the front door was more of a suggestion.
Maya Okafor AI analyst
Unrestricted file upload happens when an application accepts a file without properly checking what it is, what it's called, or where it lands. A complete fix is layered: allowlist the file types, check content rather than just the extension, store uploads where the server can't execute them, and review every upload path, not just one. A patch that blocks one extension is a blocklist, and blocklists come back.
Maya Okafor AI analyst
Out-of-bounds write is a memory-safety bug: code writes past the end of a buffer it was given, usually because a size or length was trusted or miscalculated. The real fix is correct bounds handling at the root, and the vendor should hunt for sibling bugs in the same code. The bigger problem is supply chain. Brotli is a library, and libraries get embedded in other products, so your exposure may be in software you never listed as using it.
Maya Okafor AI analyst
A buffer that writes outside its assigned space. Very ambitious. Not a quality you want in a memory allocation.
Jordan Pike AI host
Ambition is great. Just not in a compression library.
Jordan Pike AI host
Priorities. You've got two exploited bugs and finite hours. Which one goes first? Dex.
Dex Moreno AI analyst
Magento first. It's in CISA's catalog with a federal deadline, storefronts are typically internet-facing, and exposure beats severity. The Brotli score looks scary, but you can patch only what you can find. My action: list your public-facing Magento instances today, patch or isolate them, and assume someone may already have visited.
Maya Okafor AI analyst
I'd push back. Magento is one product with one owner you can identify. Brotli is the one you can't see, so the inventory takes the longest and has to start now. I'd also remind everyone that any workaround is a bridge, so give it an end date. My action: start the dependency inventory for Brotli today, and apply the fix as soon as your vendors ship one. The facts don't say what's available yet.
Sam Kowalski AI analyst
Whichever you patch first, patching isn't the end. Exploitation was already underway when CISA listed these, so assume access came earlier than the listing. Look at web server and application logs for upload activity that doesn't match your real merchants and admins. And no evidence of compromise means nothing if your logs only go back a few days. My action: preserve the logs you have right now, and find out how far back they go.
Rina Takahashi AI analyst
On attribution: the facts name no actor for either bug. CISA says attackers are exploiting them, not who they are. If a group name starts circulating, treat it as someone's claim and ask who says so and how confident they are. My action: give your leadership the exposure story, not the actor story, because the patch list is the same either way.
Rina Takahashi AI analyst
Two exploited bugs and no named group yet. I assure you the industry's naming department is working on it.
Jordan Pike AI host
Give them a minute. They'll want a logo.
Jordan Pike AI host
So, Monday: find your Magento instances and patch or isolate them, start hunting your Brotli exposure, pull the logs before they roll over, and don't wait for a threat actor name before acting. The US federal deadline for the Magento flaw is November 10, 2026. That's theirs, but it's a decent clock to borrow.