Connect with us

NEWS

PHP Ships Silent Windows Rebuilds for the Brotli Flaw

PHP rebuilt Windows 8.2 through 8.5 packages with Brotli 1.2.1, five days after PHP2Shell, and php -v will not show the change.

Published

on

PHP rebuilt its official Windows packages on October 26, 2026, five days after the PHP2Shell releases, to ship Brotli 1.2.1 against CVE-2026-111497. The runtime version is unchanged, so php -v still prints 8.5.12, 8.4.27, 8.3.36 or 8.2.35.

Shops that treated last week’s upgrade as finished still have last week’s decoder unless the zip name ends in -1. Guzzle, the HTTP client many PHP apps already ship, turns on the path PHP left off.

A Rebuild That php -v Cannot See

The PHP team posted updated Windows builds for Brotli as 8.5.12-1, 8.4.27-1, 8.3.36-1 and 8.2.35-1. Shivam Mathur, who announced the internals note, said the -1 suffix marks a Windows package rebuild with updated dependencies, not a new PHP source release.

Those zips keep the October 21 PHP2Shell fixes and replace the bundled decoder with Brotli 1.2.1. On Windows, the cURL extension can reach that decoder when automatic HTTP response decompression is on. cURL leaves that off unless an app or a client library turns it on.

The PHP project does not ship Linux or macOS binaries. Distros package PHP themselves, so this -1 zip is a Windows-only event even though the library bug is not.

THE WINDOWS REBUILD AT A GLANCE

  • The date: The 8.5.12-1 Windows zips on php.net are stamped 2026-Oct-26 13:05:05 UTC.
  • The tell: php -v stays on 8.5.12, 8.4.27, 8.3.36 or 8.2.35; only the file name gains -1.
  • The library: New builds include Brotli 1.2.1; last week’s x64 Non Thread Safe SBOMs listed Brotli 1.2.0.
  • The score: Google rates CVE-2026-111497 9.2 Critical on CVSS 4.0.

Windows PHP is often a zip dropped into a folder beside a site. A rebuild that does not bump the version string is easy to skip in that setup, which is the whole point of the -1 suffix.

Last Week’s PHP2Shell Zips Still Shipped Brotli 1.2.0

On October 21, 2026 the PHP team shipped 8.5.12, 8.4.27, 8.3.36 and 8.2.35 for two unauthenticated code-execution bugs in PHP itself, CVE-2026-109618 and CVE-2026-109619, the pair widely called PHP2Shell. Google shipped Brotli 1.2.1 the same day. The official Windows PHP zips that went out with those PHP releases still carried Brotli 1.2.0, which the SBOMs next to the x64 Non Thread Safe builds recorded.

That is why a second Windows drop existed at all. The PHP source did not need another tag. The bundled copy of Google’s decoder did.

THE FIVE DAYS FROM PHP2SHELL TO BROTLI

  1. October 21, 2026: PHP ships 8.5.12, 8.4.27, 8.3.36 and 8.2.35 for PHP2Shell, and Google ships Brotli 1.2.1.
  2. October 23, 2026: CISA records no exploitation of CVE-2026-111497 and does not list it in the Known Exploited Vulnerabilities catalog in that day’s update.
  3. October 25, 2026: Microsoft publishes a.NET advisory for the same Brotli CVE and scores it 8.1 High on CVSS 3.1.
  4. October 26, 2026: PHP publishes the -1 Windows zips with Brotli 1.2.1 inside.

Operators who only checked php -v after October 21 will see the same string they saw last week. Patching PHP2Shell did not patch the decoder sitting next to it in the Windows zip.

Why Do Guzzle Defaults Reach the Brotli Flaw?

The attack is not an inbound request to a public PHP page. It is a crafted compressed response from a server the app itself contacts. PHP’s notice names the cURL extension as the reach path when automatic decompression is enabled.

In PHP, CURLOPT_ENCODING turns that on. An empty value accepts every format cURL supports, including br. Guzzle’s 7.16.1 and 8.3.1 code sets that empty value by default for requests it sends through cURL, so an app that never touches curl_setopt can still hand Brotli bytes to last week’s Windows decoder.

WHAT HAS TO BE TRUE FOR THE HOLE TO OPEN

  • The host: Official Windows PHP from last week, with Brotli 1.2.0 still in the zip.
  • The client: cURL automatic decompression enabled, which Guzzle does unless decode_content is set to false.
  • The input: A server the app calls sends a crafted Brotli body, even if the request never asked for br.

PHP’s own notice offers no workaround for machines that cannot install the -1 zip yet. OpenAI, whose Codex Security researchers Khai Tran and Sylvie Mayer found the bug, tells operators to disable automatic Brotli decompression in HTTP clients until the update is in place, and warns that removing br from Accept-Encoding “alone does not stop a server from sending it.”

In raw PHP that means not setting CURLOPT_ENCODING, because cURL will not unpack responses without it. In Guzzle it means decode_content set to false, which also leaves gzip packed, so code that assumes a decoded JSON body will break until it unpacks the bytes itself.

The -1 suffix identifies a Windows package rebuild with updated dependencies. These builds use the same PHP source releases, and the PHP runtime versions remain unchanged.

PHP project, October 26, 2026 announcement

Laravel apps, payment clients, and anything else that speaks HTTP through Guzzle sit on that default. The decoder bug is in a library PHP did not write. The on-switch is in a client most of those apps did not configure.

The Same Decoder Hit Node.js,.NET and PHP

Google’s CVE record describes an out-of-bounds write in the Brotli decoder in versions 1.0.3 through 1.2.0. A remote attacker with no login can corrupt decoder memory, leak memory, crash the process, or potentially run code with a crafted stream. Fixed builds of the library are 1.0.10, 1.1.1 and the Brotli 1.2.1 security release.

Google’s 9.2 score is CVSS 4.0. Microsoft scored the same CVE 8.1 on CVSS 3.1 for.NET and said ASP.NET Core and HttpClient do not decompress Brotli in their default setups. Red Hat rates it 8.1 Important. Node.js called its own exposure High. The numbers disagree because the scorers are measuring different products, not because the decoder changed.

WHO SHIPPED A FIXED BROTLI COPY

Software Fixed build Default auto-decompress
PHP Windows official zips 8.5.12-1, 8.4.27-1, 8.3.36-1, 8.2.35-1 cURL off; Guzzle on
Google Brotli 1.0.10, 1.1.1, 1.2.1 Library only
Microsoft.NET 8, 9, 10, 11 October 25 advisory HttpClient off
Node.js 22.23.4, 24.22.1, 26.12.1 Shipped in the October 21 releases
Bun 1.4.4 fetch() decodes br
FrankenPHP 1.13.4 Windows and Docker images ship 1.2.1

Kévin Dunglas, who created FrankenPHP, said the 1.13.4 security release’s Docker images and Windows builds now ship Brotli 1.2.1 against CVE-2026-111497. Imperva researchers ran code through the flaw on one official Node.js build and needed several tries. PHP’s notice does not mention attacks on PHP.

The nicknames piled up as the list grew: Node2Shell, HTTP2Shell, Broccoli2Shell. They all point at the same decoder. PHP’s Windows zip was simply a late copy.

Linux PHP Waits on Distro Brotli

Linux PHP is not covered by the -1 zip, and it is not automatically safe either. Official PHP on Linux comes from the distro, and that PHP talks to the distro’s Brotli. A host can be on 8.5.12 for PHP2Shell and still be waiting on libbrotli.

After a distro Brotli bump, php-fpm workers have to restart or they keep the old library in memory. That is a different checklist from swapping a Windows zip, and mixing the two is how a team patches the wrong layer.

Windows remains the odd one because PHP vendors the decoder inside the official binary pack. The SBOM next to each zip is how that copy became visible: last week’s lists showed 1.2.0, and the new lists go with 1.2.1. Transparency did not prevent the miss. It documented it.

Check the Zip Name, Not the Version String

Install the new builds from PHP’s Windows downloads page. Because the PHP version itself is unchanged, the file name and the hash are the proof. The x64 Non Thread Safe 8.5.12-1 zip is named php-8.5.12-1-nts-Win32-vs17-x64.zip. Each flavor also publishes SPDX and CDX bills of materials beside the zip.

Compare the SHA-256 hash on the downloads page with the file you actually extracted. If the name has no -1, it is last week’s Brotli.

PHP 8.5.12-1 WINDOWS ZIP HASHES

Build SHA-256
VS17 x64 Non Thread Safe 2a36a2edcb7a5b9252f638fd5e4cf84d7f6e066092654220dc0b63e5cf4e9723
VS17 x64 Thread Safe 0dacd6484b092b5e9ae9fa3d7f96a937caf9d874eee2d980b68ed3129741144a
VS17 x86 Non Thread Safe 3a8af36358704905feaf346d63ee2d3f70474689ff74f028fa9c8c66008ca01d
VS17 x86 Thread Safe c08cc8930824ec2cf0654aaeb174c7475a84eca39c0ceefaa1eaaf1fe0564d93

IIS with FastCGI wants the Non Thread Safe zip. Apache loading PHP as a module wants Thread Safe. A second PHP copy hiding in a toolchain, a CI image, or a packaged Windows app is a separate replace. php -v will bless all of them.

Frequently Asked Questions

Which PHP Windows Builds Include Brotli 1.2.1?

Every current official Windows flavor of 8.5.12-1, 8.4.27-1, 8.3.36-1 and 8.2.35-1, including VS17 x64 and x86, thread-safe and non-thread-safe. The 8.5.12-1 x64 Non Thread Safe zip is 34.63MB. IIS FastCGI users want Non Thread Safe; Apache mod_php users want Thread Safe.

Why Does php -v Stay the Same After the Rebuild?

The -1 is a Windows package suffix, not a PHP version bump, so phpinfo() prints the same number as php -v. The source tarballs on the downloads page are still the October 21 files such as php-8.5.12.tar.gz; only the Windows zip name changed.

Do Linux PHP Servers Need the Windows -1 Zips?

No. PHP does not publish Linux or macOS binaries. Update the distro’s Brotli package, then restart php-fpm so running workers load the new library. A Windows -1 zip will not install on those hosts and would not be the right file if it did.

What Does Guzzle’s decode_content Option Change?

Setting decode_content to false stops Guzzle from asking cURL to unpack responses, which blocks Brotli and also gzip and deflate. Application code that reads a JSON body as already decoded will see compressed bytes until it unpacks them in userland, so it is a stopgap rather than a new default to keep.

The October 21 zips closed PHP2Shell. The October 26 zips close the decoder those zips still carried. If the file name has no -1, the second job is not done.

Harry is the editor of BUDGY APP, an independent title he owns and runs after ten years in journalism that began on a reporter's desk and ended up at the editor's. Numbers get particular attention here. A percentage in a business story is recomputed from the underlying figures before it goes live, a benchmark in a technology or gaming review is quoted with the conditions it was measured under, and a transfer fee or a lap time in the sports and auto pages is traced back to the club, the league or the timing sheet that published it. The same rule covers news, science, entertainment, lifestyle and travel: if a figure cannot be tied to a filing, a dataset, a transcript or a test Harry ran himself, it does not appear. Readers around the world see prices in the original currency with a conversion alongside. Errors are corrected in the open under a published corrections policy, with the change noted on the article. Questions about any figure reach him at support@budgyapp.com.

Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Trending