Skip to content
CVE-2026-111497: Update Brotli and verify the deployed package

CVE-2026-111497: Update Brotli and verify the deployed package

November 19, 2026

Brotli’s October 21, 2026 security releases fix CVE-2026-111497. Select the update for the library or vendor package actually used by the application, and retain evidence of the deployed dependency version.

Fixed Brotli releases

The upstream release notes identify the fix in each of these branches:

Brotli branchRelease containing the fix
1.21.2.1
1.11.1.1
1.01.0.10

Use a supported package containing the fix. For distribution packages, check the vendor’s CVE status and full package revision: a backport can retain an older upstream version label. For software that bundles Brotli, verify that product’s dependency inventory and security update instead of assuming the system library supplies its decoder.

PHP Windows rebuilds

PHP’s October 26 Windows build notice lists these dependency rebuilds with Brotli 1.2.1:

PHP source releaseUpdated Windows package
8.5.128.5.12-1
8.4.278.4.27-1
8.3.368.3.36-1
8.2.358.2.35-1

The -1 suffix identifies the package rebuild. PHP’s source release and reported runtime version remain unchanged, so a PHP version string alone cannot distinguish the original package from its rebuilt counterpart.

Do not downgrade a more recent supported installation to one of these October packages. Choose a current vendor package that includes the Brotli fix and subsequent PHP security updates. The November PHP session-fix updates address a separate CVE; keep the runtime and bundled-dependency checks in the patch record.

Verify the package that is running

Record the package source, complete package revision and dependency manifest or vendor build information for each deployment. On Windows, retain the installed archive’s package identity and vendor-provided integrity information. Confirm the service uses the intended installation directory; updating a separate CLI copy does not update a web-serving process.

For Linux packages or container images, use the relevant distribution or image provider’s advisory and package inventory. The PHP Windows rebuild notice does not establish that a Linux package or Docker image contains the fix. For bundled or statically linked Brotli, obtain the application’s fixed build rather than relying on an unrelated system-library update.

Deploy the supported update with the application’s documented maintenance procedure, then restart or replace processes that still use the previous installation. Check normal startup and application health, and record the installed package revision or resolved image digest for each instance. If a rollback restores an older package, reassess its Brotli patch status before closing the change.

Acknowledgements

This post was created with assistance from AI.

Last updated on