Another PHP vulnerability – already the third within a week

Last week's PHP2Shell attacks have barely died down and here's the next one: on 26 October, PHP's developers again released an emergency update. This is already the third serious PHP vulnerability in a week – but this time the fault lies not in PHP itself but in a bundled compression library.
This is a different bug
It's important to be clear: this isn't a repeat of last week's case. The two flaws that became known as PHP2Shell were in PHP's core and affected almost every PHP server. The new vulnerability (CVE-2026-111497) a ) is in the compression library called, developed by Google and included in PHP's official Windows packages.
How does the attack work?
Brotli's job is to unpack compressed incoming data. The faulty version can corrupt memory when processing a specially crafted compressed response, which in the worst case can even lead to running foreign code.
In PHP, this is reachable through the cURL extension – which websites use to fetch data from other servers (e.g. exchange rates, shipping fees, external APIs). The danger exists when automatic decompression is enabled. cURL doesn't do this by default, but the popular Guzzle library does by default, so many applications may be affected without knowing it. To exploit it, the attacker has to get the site to „talk to" a server they control.
Who's affected?
- Affected: the official Windows releases of PHP 8.2, 8.3, 8.4 and 8.5 that shipped with Brotli 1.2.0.
- Linux hosting: most Hungarian hosting providers use Linux, where Brotli comes from the system's own packages – there, the server's system update brings the fix. It's worth asking your provider.
- Severity: Google rated it 9.2 (critical), Red Hat 8.1 (important). No mass exploitation is known yet, but a research group has already executed code via the flaw in lab conditions.
What should you do?
- With PHP on Windows: download the rebuilt package: 8.5.12-1, 8.4.27-1, 8.3.36-1 or 8.2.35-1. Note: the version number hasn't changed;
php -vshows the same as before – you can recognise the fixed version by the „-1" suffix and the checksum (SHA-256) published on the download page. - If you can't update right now: turn off automatic decompression. With native cURL, don't set the
CURLOPT_ENCODINGoption, and with Guzzle set thedecode_contentsetting tofalse. It's not enough to remove „br" compression from the request – the attacker's server can still send Brotli data. - Last week's update remains in place: the new packages are built from the same source code as the 21 October releases, so the PHP2Shell fix is included. But if you haven't installed that yet, really don't put it off any longer.
- On Linux: run the system update, or ask your hosting provider whether the Brotli package has been patched.
Why are so many bugs appearing at once?
In recent weeks, AI-based code analysis tools have been finding long-hidden bugs one after another – the Brotli vulnerability was also discovered by OpenAI researchers. In the long run that's good news, as software will become more secure, but in the short term you have to update more often. If you run a website, pay particular attention to security notices now.
If you're not sure whether your website's server is up to date, or you need help updating, feel free to get in touch – I'll check it and sort it out.












