Advisory · Brotli · CVE-2026-111497

Brotli CVE-2026-111497 and WordPress: the pingback route and the fix

CVE-2026-111497 is an out-of-bounds write in the Brotli decoder, fixed on 21 October 2026 and in CISA’s Known Exploited Vulnerabilities catalog since 27 October. WordPress does not ship Brotli, and a pingback still reaches it: WordPress asks libcurl to accept any encoding, and libcurl hands a Brotli reply to the system library. What has been shown against PHP is denial of service; the code-execution chains published so far target Node.js and Bun. The fix is an operating-system package and a restart, and nothing in the WordPress update stream delivers it.

This page collects the coverage of CVE-2026-111497 from the weekly briefings of 2 and 9 November 2026, oldest first. Each section is dated.

Affected
Brotli 1.0.3 through 1.2.0, as a system library used by libcurl
Fixed in
1.0.10, 1.1.1 and 1.2.1 (21 October 2026); distributions backport, so compare the package revision
Exploitation
In CISA’s KEV since 27 October; reported against Node.js and Bun. Against PHP: denial of service demonstrated
After updating
Restart everything that had the old library loaded; rebuild container images

2 November · Brotli · CVE-2026-111497

Brotli: WordPress does not ship it, and a pingback still reaches it

CVE-2026-111497 is an out-of-bounds write in the Brotli decoder, affecting 1.0.3 through 1.2.0 and fixed on 21 October in 1.0.10, 1.1.1 and 1.2.1. CISA added it to the Known Exploited Vulnerabilities catalog on 27 October with a 10 November deadline. It is a library bug, not a WordPress one, and that is exactly why it belongs here: the fix is a package on the server, and nothing in the WordPress update stream will ever deliver it.

Patchstack’s 30 October analysis traces the route. An unauthenticated pingback.ping call to xmlrpc.php makes WordPress fetch the attacker’s source URL with wp_safe_remote_get(). WordPress’s cURL transport sets CURLOPT_ENCODING to an empty string on every request, which asks libcurl to accept and decompress any encoding the server offers; a reply with Content-Encoding: br is therefore decompressed by the system’s Brotli library inside curl_exec(), before PHP or WordPress sees a byte of the body. The same decoder is reached by oEmbed fetches, feed fetches through SimplePie, and any plugin that fetches a visitor-supplied URL. PHP’s own note on its 26 October Windows rebuilds says the vulnerable decoder is reachable through the cURL extension only when automatic decompression is enabled, which is off by default; WordPress turns it on.

What has been demonstrated against PHP is denial of service. A lab published on 27 October showed a worker killed outright and, with a payload under 100 bytes, a worker pinned at full CPU. No public, reproducible code-execution chain exists against PHP behind Apache or PHP-FPM; the chains that do exist target stock Node.js and Bun binaries, and one GitHub repository claims execution against a single pinned Docker image of WordPress, which this briefing could not verify. Say DoS, and plan for the chain to arrive.

The checks and the fix, on RPM systems first:

shell
rpm -q brotli brotli-libs
dnf update brotli brotli-libs
grep -l "libbrotli.*(deleted)" /proc/*/maps 2>/dev/null | cut -d/ -f3 | sort -u

On Debian and Ubuntu, the package is libbrotli1 and the distribution backports the fix into 1.1.0, so compare the package revision rather than the version: Patchstack’s example is 1.1.0-2+b7 vulnerable and 1.1.0-2+deb13u1 patched on Debian 13, with the suffix varying by release. The third command above lists processes still holding the old library after the update; restart them, which on a web server means Apache or nginx, PHP-FPM, and anything else that links libcurl.

shell
dpkg -l libbrotli1 | tail -1
apt-get install --only-upgrade libbrotli1

Until the package is in, Patchstack’s stopgap is a must-use plugin that tells libcurl not to decompress anything WordPress fetches. WordPress then stops asking for compressed replies, and still unpacks gzip itself in PHP:

wp-content/mu-plugins/no-curl-decoding.php New file +5 lines Show the changeHide
Must-use plugin: Patchstack’s code, with the opening PHP tag a file needs
Added: <?php
Added: add_action( 'http_api_curl', function ( $handle ) {
Added:     curl_setopt( $handle, CURLOPT_ENCODING, 'identity' );
Added:     curl_setopt( $handle, CURLOPT_HTTP_CONTENT_DECODING, 0 );
Added: }, 10, 1 );

Must-use plugins load on every request and cannot be deactivated from the dashboard, so remove this file once brotli-libs or libbrotli1 is patched and every process that loaded the old library has restarted.

Figure 1 · At a glance

WordPress does not ship Brotli. A pingback reaches the system library anyway.

QuestionAnswer
AffectedBrotli 1.0.3 through 1.2.0, the system library libcurl uses
Fixed in1.0.10, 1.1.1 and 1.2.1; distributions backport, so compare the package revision
Routepingback.ping makes WordPress fetch a URL; libcurl decompresses a Brotli reply
Shown against PHPDenial of service; public code-execution chains target Node.js and Bun
After updatingRestart every service that had the old library loaded; rebuild images
The points that decide what to do about Brotli CVE-2026-111497 as it reaches WordPress through libcurl, as stated in the sections below.

9 November · Brotli · CVE-2026-111497

Brotli: the federal deadline is 10 November, and exploitation is not in doubt

Some coverage this week still describes Brotli’s CVE-2026-111497 as contested. CISA added it to the catalog on 27 October with a 10 November deadline, and Sophos and ELLIO have both reported exploitation, so treat it as exploited. The exploitation reported so far targets Node.js and Bun, where public code-execution chains exist; against PHP, the route from WordPress through a pingback and libcurl that last week’s briefing walked through has been shown to crash or pin a worker, not to run code. Node.js fixed it on 21 October in 22.23.4, 24.22.1 and 26.12.1, and Microsoft shipped out-of-band .NET updates on 25 October.

For a WordPress host the work is unchanged: the operating system’s brotli-libs or libbrotli1 by package revision, a restart of everything that had the old library loaded, container images rebuilt, and Node.js updated separately wherever a build pipeline or a headless front end runs it.

shell
grep -l "libbrotli.*(deleted)" /proc/*/maps 2>/dev/null | cut -d/ -f3 | xargs -r ps -o pid,comm -p
node -v 2>/dev/null

Common questions

Common questions about Brotli and WordPress

Does updating WordPress fix the Brotli flaw?

No. WordPress does not ship Brotli; it asks libcurl to decompress whatever a remote server sends, and libcurl uses the operating system’s Brotli library. The fix is the brotli-libs or libbrotli1 package, a restart of every process that had it loaded, and a rebuild of container images. Blocking xmlrpc.php removes the pingback route only; Patchstack’s must-use plugin that sets the cURL encoding to identity covers the rest until the package is in.

Choose the response path

A library below PHP needs checking on every host: choose the response path.

The server under the sites

Get both halves of the PHP2Shell chain checked and proven on every host.

Best when several servers need PHP and the kernel verified from the running process rather than the repository, the Core update window and the published addresses searched in the logs, and the post-exploitation look-back done once, with a written result per host.

One site, one worrying result

Get the finding classified and the site restored to a trusted state.

Best when an exploited booking, membership or form plugin left an administrator or a PHP file behind, a plugin with no fix was installed, or a cleaned site has come back, and you want every layer removed in one pass rather than one at a time.