Brotli flaw added to KEV, patch quickly
Brotli, Magento, Node2Shell exploited ·
In this episode
The facts
- Attackers are exploiting CVE-2026-111497, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- Attackers are exploiting CVE-2026-48356, according to CISA.
- Attackers are exploiting Node2Shell, according to Sophos.
- Attackers are reported to be exploiting Brotli.
- A fix is available for Node.js.
- A fix is available for CVE-2026-111497.
- CVE-2026-111497 is a flaw in Google Brotli.
- CVE-2026-48356 is a flaw in Adobe Commerce and Magento.
Sources
The panel
Jordan Pike AI host
CISA says attackers are exploiting CVE-2026-111497 and have added it to its Known Exploited Vulnerabilities catalog. CISA also reports exploitation of CVE-2026-48356. Sophos says attackers are exploiting Node2Shell. Help Net Security reports exploitation of Brotli, which has not been confirmed.
Jordan Pike AI host
CVE-2026-111497 is a flaw in Google Brotli, while CVE-2026-48356 affects Adobe Commerce and Magento. The Hacker News reports a fix is available for Node.js, and Rapid7 says a fix is available for CVE-2026-111497.
Jordan Pike AI host
So who should care? Any organization running web services that use Brotli, Adobe Commerce, or Node.js. Dex, give us the attack picture.
Dex Moreno AI analyst
Components like these tend to sit on the edge of the network, which is why a KEV entry is an emergency whatever the score. If an attacker reaches a vulnerable web service, the prize is rarely the box itself. It's the stored credentials and the trust that box has into internal services, and a commerce platform can sit close to customer data. Patch or isolate the affected systems within 72 hours.
Dex Moreno AI analyst
Zero-budget exploit? The attackers must have funded it with the company coffee fund.
Jordan Pike AI host
I'll alert accounting. For unrelated reasons.
Maya Okafor AI analyst
The public details don’t spell out the exact bug class for the Brotli issue or the Adobe Commerce flaw, so we can’t say whether it’s a memory-corruption bug, an auth bypass, or something else. What we do know is that exploitation is already observed, so the risk surface is real. A complete fix would involve upstream code changes that validate input lengths and enforce proper bounds, while a partial fix might just block the offending request pattern. Until we see the full root-cause, apply the vendor patches that are available and run a regression test to confirm the class is closed.
Dex Moreno AI analyst
I hear you, Maya, but the KEV listing makes this an emergency. Even without a full class description, the fact that attackers are already in the wild means we can’t wait for a deep dive. Patch now, then do the post-mortem.
Maya Okafor AI analyst
We agree on patching now. Where we differ is that the post-mortem can't wait until later, because a patch that ships without root-cause analysis tends to come back. Ask your vendors what the bug class was and whether the fix closes the whole class or one path. Also inventory everywhere Brotli lives, since a library like this often rides inside other products. And if you use a stopgap, give it an end date.
Sam Kowalski AI analyst
From a response perspective, assume early access. Pull recent web server and application logs, look for unusual compressed payloads or admin logins from unknown IPs, and enable detailed Brotli decoding logs where possible. Set up alerts for any new Node2Shell binaries appearing on your hosts.
Sam Kowalski AI analyst
And check how far back those logs actually go. "No evidence of compromise" means nothing if your retention window is shorter than the time the flaw was exposed. Preserve what you have before you start patching and rebuilding.
Rina Takahashi AI analyst
Both CISA and Sophos attribute these exploits to unnamed threat actors; the lack of a specific group suggests opportunistic actors leveraging publicly available exploit code. Keep an eye on updates to the KEV feed and share any IOCs you discover with peers.
Rina Takahashi AI analyst
One note on confidence: the Brotli exploitation from Help Net Security is unconfirmed, so treat it as a claim. The CISA and Sophos statements are the firmer ground to prioritise from. My action is to watch the KEV catalog for updates and re-rank as they land.
Jordan Pike AI host
Bottom line: if you run Brotli, Adobe Commerce or Node.js, patch immediately, monitor your logs, and update your threat feeds. That’s the Monday checklist.