HTTP2Shell: a critical Brotli flaw forces emergency .NET and PHP for Windows patches — what to update today on the servers of your Mexico operation
On October 26, a critical flaw called HTTP2Shell was disclosed in Brotli. Brotli is the library that compresses what a web server sends to the browser so pages load faster. The same day Microsoft shipped emergency .NET patches, as BleepingComputer reported, and PHP released its second Windows security update in five days.
This is not PHP2Shell, which we covered here. It is a different flaw. And on October 27 CISA confirmed that two PHP2Shell flaws are already being exploited, according to The Hacker News. The run of remote code execution bugs is real.
Is your Mexico site affected? Windows servers, IIS and .NET apps
Headquarters may patch its own data center fast. The risk sits in what was set up locally:
- A Windows server with IIS, Microsoft’s web server, hosting a supplier portal, an intranet or an internal system.
- A custom .NET app built by a local vendor: the quoting tool, production tracking, the warehouse system.
- A PHP system running on Windows, more common than you would think in older internal tools.
If none of that exists at your Mexico site, good. Still check PHP versions on any web hosting, because of PHP2Shell.
How to tell in ten minutes
| What to check | How | What you are looking for |
|---|---|---|
| .NET runtime | On the server: dotnet --list-runtimes | Installed versions vs. Microsoft’s advisory |
| Self-contained .NET apps | Ask the vendor who built it | They ship their own .NET: rebuild needed |
| PHP on Windows | php -v and php -m | Version and loaded modules |
| IIS | IIS Manager, Compression section | Whether compression is on and which module |
A self-contained app carries its own copy of .NET inside its folder. Patching the server does not touch it. In our experience, it is the one everybody forgets, especially when the original vendor is long gone.
Patch order that will not break the app
- Take a backup or snapshot, an instant copy of the virtual machine you can roll back to in minutes.
- Start with anything internet-facing: customer and supplier portals.
- Test on a copy or during low-traffic hours, ideally outside your plant’s shift change.
- For .NET, install the new runtime and the Hosting Bundle, then restart IIS with
iisreset. - For PHP, swap the binaries while keeping your
php.iniand extensions. - Rebuild and redeploy self-contained apps.
- Test what matters: log in, stamp a CFDI invoice, run a report.
What breaks the app is rarely the patch. It is an overwritten php.ini or a missing Hosting Bundle.
What to check in the logs afterwards
Patching closes the door. Logs tell you whether someone already walked in.
- IIS logs (
C:\inetpub\logs\LogFiles): spikes of 500 errors, requests to paths that do not exist, one unknown IP hammering the same endpoint. - Event Viewer:
w3wp.exe(the IIS process) orphp-cgi.exelaunchingcmdor PowerShell. That is not normal. - New
.aspxor.phpfiles in the web folder that nobody uploaded. - Recent local users or scheduled tasks.
What about your Mexico operation?
If nobody can tell you which .NET or PHP version runs on the local servers, that is your answer: you need an inventory.
Our IT support plans include server inventory and patching, plus maintenance of custom systems, with on-site hands across Mexico and reporting in English. For the bigger picture this month, see the October 2026 Patch Tuesday.
Book your free assessment — we reply the same business day.
Your path
Running IT in Mexico from abroad
62 of 89- Unpatched PHP ✓ Read You are here 3 min
- Server 2016 ✓ Read You are here 4 min
- HTTP2Shell ✓ Read You are here 3 min
- Qilin and backups ✓ Read You are here 3 min
- NAS ransomware ✓ Read You are here 3 min
- Ivanti VPN ✓ Read You are here 4 min
- Protect laptops ✓ Read You are here 4 min
- Field services →