Published October 30, Patchstack’s report on the WordPress Brotli vulnerability describes a route from an unauthenticated XML-RPC pingback to a PHP worker crash. The flaw is in Google’s Brotli decoder, which WordPress can reach through the operating system’s libcurl library when it fetches an attacker-controlled URL.
The short answer: WordPress does not bundle the vulnerable Brotli decoder, so updating WordPress or a plugin does not fix the underlying issue. Update the system Brotli package and rebuild affected images. Until then, disabling pingbacks can close one route, but it does not cover other WordPress features or plugins that fetch URLs.
What the WordPress Brotli vulnerability means for sites
CVE-2026-111497 is an out-of-bounds write in Brotli. Patchstack says it affects versions 1.0.3 through 1.2.0 and has a CVSS score of 9.2. The fixes are Brotli 1.0.10, 1.1.1 and 1.2.1, released October 21, 2026.
The attack path is indirect. An attacker sends a pingback request to a site’s xmlrpc.php endpoint and supplies a source URL they control. WordPress fetches that URL; if the attacker’s server replies with a malformed Brotli-compressed body, libcurl processes it before WordPress receives the response.
That detail changes where site owners should look. There is no plugin version to update, and the malicious compressed data arrives in the reply to an outbound request, not in the original incoming request. Patchstack’s reported, reproduced impact is a worker crash or a worker pinned at 100% CPU. The report says remote code execution has not been established for the WordPress path.
Which WordPress request paths are exposed?
Pingbacks are the clearest unauthenticated route, but the decoder is reached by WordPress outbound HTTP more broadly. The affected paths depend on how the site is configured and which plugins it runs.
| Path | Access described by Patchstack |
|---|---|
pingback.ping through xmlrpc.php | No account is needed; the site must have a pingable published post. |
| A plugin or theme fetching a visitor-supplied URL | Depends on the plugin or theme endpoint; Patchstack says it can require no account. |
| oEmbed discovery or the oEmbed proxy | Contributor-level access or higher. |
| A SimplePie feed fetch | Requires an administrator-configured feed. |
Disabling XML-RPC at the web server or removing the pingback method can reduce exposure through that route. But Patchstack warns that the common xmlrpc_enabled filter does not disable unauthenticated pingbacks. Blocking xmlrpc.php also leaves oEmbed, feeds and plugin-driven URL fetches untouched.
Update Brotli, not just WordPress
The permanent fix is to update the Brotli library supplied by the operating system and rebuild the affected image. Patchstack specifically notes that pulling the current wordpress:latest image does not help if its installed libbrotli1 package remains vulnerable. Site operators using containers should check the package inside the image, rather than assume a fresh pull includes the fix.
Version checks need care on Debian and Ubuntu. Patchstack says those distributions can backport the fix while retaining the upstream 1.1.0 version number. In that case, the package revision shows whether the fix is present. Check the distribution’s security update status and package revision, then rebuild and redeploy the image.
If an immediate package update is not possible, the report describes a temporary code-level measure: stop libcurl from automatically decoding Brotli responses. That can cover more request paths than blocking XML-RPC, but it is a mitigation, not a fix. Blocking pingbacks is a narrower stopgap and does not protect other URL-fetching features.
What site owners should check now
First, ask the hosting or platform team which Brotli package revision runs in the production environment and whether the affected image has been rebuilt. For self-managed containers, verify the package inside the image that actually runs WordPress. Do not rely on the WordPress version alone to determine exposure.
Next, confirm whether xmlrpc.php is blocked at the server or whether only an XML-RPC setting has been changed. Review plugins and themes that fetch visitor-supplied URLs, since those requests can reach the same decoder. Patchstack also recommends watching outbound traffic and server logs for unusual compressed responses, worker crashes or PHP workers stuck at full CPU.
Patchstack reported that CISA added the CVE to its Known Exploited Vulnerabilities catalog on October 27, with a November 10 remediation deadline for federal agencies. That date is a federal deadline, not a WordPress release date or a general deadline for every site owner. It does make the package update a concrete operational task rather than something to defer.
FAQ
Does updating WordPress fix CVE-2026-111497?
No. The flaw is in the Brotli decoder supplied by the operating system and used through libcurl. Update the relevant system package and rebuild the environment running WordPress.
Does disabling XML-RPC fully protect a site?
No. Blocking the endpoint or disabling pingbacks closes the pingback route, but oEmbed, feeds and plugins that fetch URLs may still reach the decoder. Treat XML-RPC blocking as a limited mitigation.
Has remote code execution been confirmed through WordPress?
Patchstack reports that the WordPress path has been reproduced as a worker crash or CPU exhaustion. Its report says blind remote code execution is not established for this path.
Next step: check the Brotli package revision in the production host or container, then update and rebuild wherever the vulnerable package remains installed.