PHP Windows Brotli Fix: Check for the -1 Rebuilt Packages

PHP rebuilt its official Windows 8.2–8.5 packages with Brotli 1.2.1. Check exact package provenance, the -1 rebuild suffix, and cURL decompression reachability.

Reader ratingRate this article

Loading reader rating…

Privacy-conscious voting uses a signed random browser identifier and a short-lived network hash; the rating tables contain no raw IP-address column.

Reader ratings require JavaScript; the article remains fully readable without it.

Security advisory • PHP Windows package rebuilds

The PHP project has rebuilt its official Windows packages for PHP 8.2 through 8.5 with Brotli 1.2.1, addressing CVE-2026-111497 in a conditional cURL decompression path.[1]

Reporting cutoff: October 26, 2026, 3:05 p.m. EDT / 19:05 UTC. This is a patch and inventory advisory, not evidence that a system was compromised.

Decision: If you run an official PHP Windows package in the affected branches, verify the package provenance and move to the matching -1 rebuild. Give priority to applications or HTTP-client libraries that enable automatic response decompression and can receive an attacker-controlled Brotli response.[1]

What changed

On October 26, PHP announced four rebuilt Windows packages: 8.5.12-1, 8.4.27-1, 8.3.36-1 and 8.2.35-1. They bundle Brotli 1.2.1, which fixes CVE-2026-111497, an out-of-bounds write in Brotli decompression.[1] Google’s Brotli 1.2.1 release describes the upstream issue as an out-of-bounds write that permits remote code execution.[2]

Who is affected—and who is not

The PHP-specific affected path is narrow: an official PHP Windows build from one of the four maintenance branches, with the bundled vulnerable decoder, where the cURL extension performs automatic HTTP-response decompression on attacker-controlled Brotli content. PHP says automatic decompression is disabled by default in cURL, although applications and HTTP-client libraries can enable it.[1]

  • This notice does not establish that all PHP installations are affected.
  • It does not identify Linux PHP packages as part of this Windows-package rebuild.
  • Having an older package is an exposure signal, not proof of exploitation or compromise.
  • No claim is made here about CISA KEV status or observed exploitation.

Fixed Windows package builds

Maintenance branch Rebuilt package to verify What stays the same
PHP 8.5 8.5.12-1 PHP runtime version 8.5.12
PHP 8.4 8.4.27-1 PHP runtime version 8.4.27
PHP 8.3 8.3.36-1 PHP runtime version 8.3.36
PHP 8.2 8.2.35-1 PHP runtime version 8.2.35

PHP says the -1 suffix identifies a Windows package rebuild with updated dependencies; the PHP source release and runtime version remain unchanged.[1]

Why php -v may not show the rebuild

Because the runtime version is unchanged, php -v may report only 8.5.12, 8.4.27, 8.3.36 or 8.2.35 and omit the distribution’s -1 package-rebuild suffix. Do not classify the package from that command alone; use the download archive, package filename, deployment record, installer inventory, software-distribution log or recorded checksum that identifies the exact Windows package you installed.[1]

Safe patch and validation steps

  1. Inventory provenance before changing anything. Record the executable path, PHP branch, package filename or archive, installation source, architecture and thread-safety build. Identify every service, scheduled task and application pool that loads that runtime.
  2. Check whether the path is reachable. Review the application’s cURL options and HTTP-client-library configuration for automatic response decompression. Treat “compiled in” and “enabled on an attacker-reachable request path” as separate facts.[1]
  3. Obtain the matching official rebuild. Use the PHP Windows download linked by the PHP announcement and verify the vendor-published package identity before deployment.[1]
  4. Stage under normal change control. Back up configuration and extensions, confirm architecture/thread-safety compatibility, and test application startup plus outbound HTTP workflows.
  5. Replace every running worker. Restart or recycle the relevant Windows services and application pools so old processes do not continue using the earlier bundled library.
  6. Verify package provenance again. Confirm the deployed archive or package record carries the matching -1 rebuild, then test representative HTTP requests including expected compressed-response handling.
  7. Watch for regressions, not imagined compromise. Review service health and error logs after rollout. An older package alone does not show that exploitation occurred.

Temporary risk reduction: if an immediate update is impossible, assess whether automatic Brotli response decompression can be disabled without breaking the application. This is practical containment, not a substitute for installing the rebuilt package.

What remains unknown

The primary sources reviewed at the cutoff do not establish which third-party PHP HTTP clients enable this path in any particular environment, whether downstream packaged products have incorporated the rebuild, or whether a given system was exploited. Confirm those points from the application’s configuration, supplier guidance and local telemetry; do not infer them from the version alone.

Sources

  1. PHP — Updated PHP Windows builds for Brotli security fix (live page refreshed October 26, 2026).
  2. Google Brotli — v1.2.1 release (live release refreshed October 26, 2026).

Disclosure: Updated October 26, 2026 at the reporting cutoff above. Hero image is AI-generated editorial illustration, not official PHP, Microsoft, Google or Brotli artwork.