NEWS
PHP Windows Rebuild Hides the Brotli Fix From php -v
PHP’s Oct. 26 Windows -1 rebuilds fix CVE-2026-111497 without changing php -v, colliding with CISA’s PHP2Shell version list.
PHP shipped emergency Windows rebuilds on Oct. 26 for CVE-2026-111497, a Brotli decoder bug, without changing the runtime version. The packages are 8.5.12-1, 8.4.27-1, 8.3.36-1 and 8.2.35-1. They bundle Brotli 1.2.1 and keep the Oct. 21 PHP source, so php -v still prints 8.5.12, 8.4.27, 8.3.36 or 8.2.35.
That collision landed on the same calendar day CISA added PHP2Shell to its Known Exploited Vulnerabilities catalog and told operators to move to those four numbers. A Windows host can pass a version check for last week’s inbound PHP bugs and still load the decoder Google scored 9.2 under CVSS 4.0.
php -v Cannot Tell the Rebuild Apart
The PHP team posted updated Windows builds for Brotli after Google’s library fix, and Shivam Mathur carried the same notice on the PHP Foundation Discourse. The -1 suffix marks a Windows package rebuild with refreshed dependencies. The runtime versions have not changed.
The PHP Foundation account posted the rebuilds on Oct. 26.
Rebuilt Windows binaries with updated brotli version are available: https://t.co/UlsD3aK9PX#php #windows
— The PHP Foundation (@ThePHPF) October 26, 2026
Official Windows builds reach the buggy decoder through the cURL extension when automatic HTTP response decompression is on. cURL leaves that off unless a caller turns it on. Application HTTP clients can flip it anyway, which is why a version string is a weak close-out for this ticket.
THE OCT. 26 WINDOWS REBUILDS
| PHP branch | Rebuild package | php -v still prints |
|---|---|---|
| PHP 8.5 | 8.5.12-1 | 8.5.12 |
| PHP 8.4 | 8.4.27-1 | 8.4.27 |
| PHP 8.3 | 8.3.36-1 | 8.3.36 |
| PHP 8.2 | 8.2.35-1 | 8.2.35 |
A scanner that stores only the runtime release will treat the Oct. 21 zip and the Oct. 26 zip as the same artifact. The file name and the SHA-256 on PHP’s Windows downloads page are the identifiers that actually move.
CISA’s KEV List Names the Same PHP Releases
On Oct. 21, PHP published 8.5.12, 8.4.27, 8.3.36 and 8.2.35 for CVE-2026-109618 and CVE-2026-109619, the pair known as PHP2Shell. Those bugs sit in PHP’s own request handling. They can give unauthenticated remote code execution on installs that serve web requests, including PHP-FPM, php-cgi, FrankenPHP, LiteSpeed and Apache with mod_php, which PHP called the highest risk.
CISA revised its PHP alert on Oct. 26 and recorded that it had added both PHP2Shell identifiers to the KEV catalog that day. Federal civilian agencies work off that list on a fixed deadline. The CISA PHP2Shell patching alert still tells operators to install the four runtime versions that php -v reports after the Brotli rebuild as well as before it.
Organizations should immediately update to PHP 8.5.12, 8.4.27, 8.3.36, or 8.2.35 to fix these vulnerabilities.
CISA, alert on critical PHP vulnerabilities, revised Oct. 26, 2026
That sentence is right for PHP2Shell and incomplete for Windows PHP’s bundled Brotli. The KEV item does not name CVE-2026-111497. A ticket closed as “PHP updated to 8.5.12” can still be running the Oct. 21 Windows zip.
THE FIVE DAYS BETWEEN THE TWO PHP DROPS
- October 21, 2026: Google ships Brotli 1.2.1, 1.1.1 and 1.0.10. Node.js ships 22.23.4, 24.22.1 and 26.12.1. PHP ships 8.5.12, 8.4.27, 8.3.36 and 8.2.35 for PHP2Shell.
- October 25, 2026: Microsoft ships out-of-band.NET 8.0.33, 9.0.22, 10.0.14 and.NET 11 Release Candidate 3 for the same Brotli CVE.
- October 26, 2026: PHP publishes the four Windows -1 packages. CISA adds PHP2Shell to KEV. FrankenPHP 1.13.4 ships with Brotli 1.2.1.
Some notes also reused an HTTP2Shell label for the Brotli bug, which collides with PHP2Shell and sends a search to the wrong CVE. Track CVE-2026-111497 for the decoder and the two 1096xx identifiers for the inbound PHP flaws.
How the Decoder Writes Past an Eight-Byte Buffer
Google, the CVE numbering authority, describes CVE-2026-111497 as a buffer overflow in the Brotli decoder file c/dec/decode.c on versions 1.0.3 through 1.2.0. A crafted compressed stream can corrupt adjacent decoder state, disclose memory, crash the process, or run code. The CVSS 4.0 vector is CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. Weaknesses listed are CWE-787 (out-of-bounds write) and CWE-252 (unchecked return value).
OpenAI Codex Security researchers Khai Tran and Sylvie Mayer reported the flaw. Node.js, which bundled the same decoder, published the mechanics in its Oct. 21 security release.
An invalid block switch was reported as a temporary need for more input instead of a permanent format error, so the streaming decoder kept appending input bytes to an eight-byte internal buffer.
The Node.js Project, Oct. 21, 2026 security releases
That eight-byte internal buffer is the whole primitive. PHP’s Oct. 26 note does not report attacks on its Windows builds. Microsoft’s Security Update Guide, updated Oct. 26, listed the Brotli CVE as publicly disclosed, not exploited, with an “Exploitation More Likely” flag for.NET.
Working exploits against one runtime do not transfer to PHP’s Windows zip by default. They do show that the shared C decoder is not a paper crash on every build that unpacks attacker-controlled Brotli.
Default Guzzle Settings Reach the Vulnerable Decoder
PHP’s documented path is the application acting as an HTTP client. It calls another server, gets a compressed body, and hands that body to Brotli. Public-facing PHP is the PHP2Shell problem. This one starts on outbound fetches.
libcurl’s CURLOPT_ACCEPT_ENCODING both writes the Accept-Encoding header and turns on automatic decompression. The documented default is NULL, which sends no such header and does not decode. An empty string asks for every encoding the build supports, including br. A server can still return a Content-Encoding the client did not list, so stripping br from an outgoing header is not proof the decoder is unreachable.
Guzzle, the HTTP client many PHP apps sit on, documents a decode_content default of true. That setting decodes gzip, deflate and other Content-Encoding bodies unless the app turns it off. It does not make every Guzzle install exploitable. Exposure still depends on the handler, the Windows PHP build under it, and whether an attacker can shape the compressed bytes. It does mean cURL’s default is the wrong place to stop the review.
WINDOWS PHP PATHS WORTH CHECKING FIRST
- User-supplied URLs: Features that fetch a link a user pastes, including previews, importers and “fetch this feed” jobs.
- Outbound webhooks: Workers that call customer endpoints and decode whatever body comes back.
- Guzzle and cousins: Clients that leave decode_content on and sit on the Windows cURL extension.
- Secondary runtimes: Scheduled tasks, queue workers and CLI copies that load a different php.exe than the web pool.
Setting decode_content to false stops Guzzle from unpacking the body. Gzip and deflate then arrive compressed too, so json_decode on the raw bytes will fail, and handing those bytes to a second vulnerable decoder leaves the hole open. Test that change before it goes near production.
A Separate Brotli Copy in Every Runtime
The Brotli 1.2.1 security release is dated Oct. 21, the same day as 1.1.1 and 1.0.10 on the older branches. Those three tags are the upstream close. They do not replace a copy compiled into PHP, Node.js, Bun or.NET. An operating-system libbrotli update also does not rewrite those binaries.
FIXED BUILDS FOR THE SAME DECODER
| Product | Fixed builds |
|---|---|
| Google Brotli | 1.2.1; also 1.1.1 and 1.0.10 on older branches |
| PHP Windows | 8.5.12-1, 8.4.27-1, 8.3.36-1, 8.2.35-1 |
| Node.js | 26.12.1, 24.22.1, 22.23.4 |
| .NET | 8.0.33, 9.0.22, 10.0.14,.NET 11 RC3 |
| Bun | 1.4.4 |
Rahul Bhandari, a Microsoft senior program manager, said the Oct. 25.NET out-of-band release should be installed as soon as possible. Microsoft also said Brotli decompression is off in a stock.NET or ASP.NET Core install until an app opts into request or HttpClient decompression or calls the Brotli APIs directly. Envoy and Istio published their own fixes for deployments that enable a Brotli decompressor. Each of those is a separate change-control item.
Kévin Dunglas, who created FrankenPHP, said the 1.13.4 security release on Oct. 26 put Brotli 1.2.1 into its Docker images and Windows builds. A PHP shop that patched php.exe and left a FrankenPHP image on 1.13.3 still has the old decoder in that process.
Docker images and Windows builds now ship Brotli 1.2.1 against CVE-2026-111497 (Node2Shell), and Windows and macOS binaries are built with Go 1.27.3.
Kévin Dunglas, FrankenPHP creator, on X, Oct. 26, 2026
Which Windows Packages Replace the Oct. 21 Builds?
For official Windows PHP, the job is the matching -1 zip for the branch in use, then a process restart so workers load the new binary. Background jobs, scheduled tasks and extra installs each need their own check, because a web pool can be current while a queue runner still points at the Oct. 21 directory.
Until that zip is in place, turning off automatic response decompression removes the path PHP documented, if the change is applied in cURL, Guzzle and any other client the app uses. It is a hold, not a patch. PHP’s announcement did not describe a complete workaround inside the runtime.
WHAT WE KNOW
- Windows packages: 8.5.12-1, 8.4.27-1, 8.3.36-1 and 8.2.35-1 bundle Brotli 1.2.1 and keep the Oct. 21 PHP source.
- Client path: PHP names cURL automatic decompression as the route on those builds, with Guzzle’s default decode_content able to enable it.
- KEV status: CISA listed PHP2Shell (CVE-2026-109618 and CVE-2026-109619) on Oct. 26, not the Brotli CVE.
WHAT IS UNCONFIRMED
- PHP Windows exploits: No public write-up has shown code execution against the official Windows PHP zips the way Node.js builds have been tested.
- In-the-wild Brotli use: Microsoft still recorded no exploitation of CVE-2026-111497 as of its Oct. 25.NET advisory.
Replacement zips sit on PHP’s Windows downloads page under the same 8.5.12, 8.4.27, 8.3.36 and 8.2.35 headings as the Oct. 21 builds. The suffix in the file name is the record that the decoder moved.
Frequently Asked Questions
How Can I Confirm a Windows PHP Install Is the Brotli Rebuild?
Compare the zip’s SHA-256 with the hash on PHP’s Windows downloads page, and confirm the file name carries -1 after the version. Thread-safe and non-thread-safe packages are separate downloads, so the matching -1 file for that ABI has to be the one that replaced the Oct. 21 copy. phpinfo() and php -v will still show 8.5.12, 8.4.27, 8.3.36 or 8.2.35 after a correct install.
Is CVE-2026-111497 Part of PHP2Shell?
No. PHP2Shell is CVE-2026-109618 and CVE-2026-109619, which PHP described as out-of-memory corruption and stale request state on servers that handle HTTP. CVE-2026-111497 is an out-of-bounds write in Google’s Brotli decoder, reached on Windows PHP when a client unpacks a compressed response. CISA’s Oct. 26 KEV addition covers only the two PHP2Shell identifiers.
Does Removing br From Accept-Encoding Stop Decoding?
No. CURLOPT_ACCEPT_ENCODING both sets the request header and enables decoding of the Content-Encoding that actually arrives, and libcurl documents that a server may send a different encoding than the one requested. Setting CURLOPT_ACCEPT_ENCODING to NULL is the documented way to stop libcurl sending that header and decompressing the body. Dropping only the br token leaves other encodings, and a mismatched Content-Encoding can still reach a decoder.
Do Linux Servers Use These -1 Windows Packages?
No. The -1 files are Windows binaries and do not install on Linux. Linux PHP does not pick up this rebuild by version suffix; operators should follow their distribution’s Brotli or libbrotli package and any vendor PHP advisory instead of looking for 8.5.12-1 on a Unix host.
Does.NET Framework Need the Brotli Update?
Microsoft’s.NET announcements say.NET Framework is not affected. The Oct. 25 out-of-band builds that carry the Brotli fix are.NET 8.0.33, 9.0.22, 10.0.14 and.NET 11 Release Candidate 3, plus related Visual Studio and PowerShell packages listed in that release. A Framework-only Windows server is outside that set; a machine that also runs modern.NET still needs the OOB runtime if apps decode Brotli there.
-
AUTO2 months agoVolkswagen Sells the Osnabruck Plant to Clear a Board Fight
-
NEWS3 months agoApple’s Foldable iPhone Hinges on Samsung Display Supply
-
AUTO3 months agoTata Motors’ Iveco Tender Opens as Holders Still Decide
-
BUSINESS3 months agoSaksham Gaur Finds He Is His Own Company’s Client
-
TECHNOLOGY3 years agoWhat Is SD on Amazon Prime?
-
BUSINESS3 months agoHyderabad 22-Carat Gold Jumps After a False Bargain
-
GAMING3 months agoOnimusha Way of the Sword Preload Hits a Windows 11 Wall
-
ENTERTAINMENT2 years agoAndy Scott’s Steel Loon Repeats the Kelpies Regeneration Bet
