Executive Summary
In October 2026, PHP issued emergency Windows package rebuilds for versions 8.2 through 8.5 to address CVE-2026-111497, a critical memory-corruption remote code execution flaw in the bundled Brotli compression library (versions prior to 1.2.1). The vulnerability is reachable through PHP's cURL extension when automatic HTTP response decompression is enabled—a default behavior in the widely-used Guzzle HTTP client library. Rated 9.2 (Critical) on CVSS 4.0 by Google, the flaw allows a malicious server to deliver a crafted compressed response that corrupts process memory, potentially executing arbitrary code. The rebuilt packages arrive just five days after emergency patches for two separate PHP2Shell RCE flaws, underscoring a compounding supply-chain risk for Windows-hosted PHP environments.
This incident illustrates the compounding risk of software supply chains where third-party compression libraries bundled inside language runtimes become silent attack surfaces. With Guzzle enabling automatic Brotli decompression by default and PHP shipping SBOMs only post-facto, organizations relying on PHP-based web applications—particularly in regulated industries—face renewed urgency around dependency visibility and patch velocity.
Why This Matters Now
PHP serves a significant share of the world's web infrastructure, and this is the second critical RCE patch issued in five days for Windows builds. The flaw is exploitable through default Guzzle settings—meaning millions of applications are silently exposed without any misconfiguration. With no known workaround short of disabling all automatic decompression, and active research demonstrating exploitability on related runtimes like Node.js, organizations must act immediately to inventory, patch, and verify affected PHP deployments.
Attack Path Analysis
An attacker exploits CVE-2026-111497, a critical memory corruption flaw in the Brotli decompression library bundled with official PHP Windows packages, by serving a crafted compressed HTTP response to a vulnerable PHP application using Guzzle or any cURL-based client with automatic decompression enabled. Successful exploitation yields remote code execution on the Windows host running PHP, after which the attacker escalates privileges, moves laterally across internal workloads, establishes command-and-control channels, and exfiltrates sensitive data before causing broader operational impact.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
The attacker positions a malicious server or performs an adversary-in-the-middle interception to deliver a crafted Brotli-compressed HTTP response to a PHP Windows application using cURL with CURLOPT_ENCODING enabled (e.g., via Guzzle defaults). The malformed Brotli payload triggers CVE-2026-111497, causing a heap memory corruption in the Brotli decoder (libbrotli) bundled with PHP 8.2-8.5 Windows builds prior to the -1 rebuild, achieving remote code execution on the PHP process.
Related CVEs
CVE-2026-111497
CVSS 9.2A memory corruption vulnerability in the Brotli compression library (versions prior to 1.2.1, 1.1.1, and 1.0.10) allows a remote attacker to corrupt memory and potentially execute arbitrary code by serving a crafted compressed HTTP response to an application using automatic Brotli decompression via cURL or compatible HTTP clients such as Guzzle.
Affected Products:
Google Brotli – < 1.0.10, < 1.1.1, < 1.2.1
PHP Group PHP for Windows – 8.2.x < 8.2.35-1, 8.3.x < 8.3.36-1, 8.4.x < 8.4.27-1, 8.5.x < 8.5.12-1
Exploit Status:
no public exploitReferences:
https://www.php.net/archive/2026.php#2026-10-26-1https://github.com/google/brotli/releases/tag/v1.2.1https://discourse.thephp.foundation/t/announce-updated-php-windows-builds-for-brotli-security-fix/6324https://nvd.nist.gov/vuln/detail/CVE-2026-111497https://access.redhat.com/security/cve/CVE-2026-111497https://www.cisa.gov/known-exploited-vulnerabilities-catalog
MITRE ATT&CK® Techniques
Exploitation for Client Execution
Exploit Public-Facing Application
Compromise Software Supply Chain
Application Layer Protocol: Web Protocols
Command and Scripting Interpreter: Unix Shell
Exploitation for Defense Evasion
Data Encrypted for Impact
Obtain Capabilities: Vulnerabilities
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – All System Components Protected from Known Vulnerabilities via Patching
Control ID: Requirement 6.3.3
NYDFS 23 NYCRR 500 – Vulnerability Management and Incident Response Readiness
Control ID: Section 500.7 — Access Privileges & Section 500.16 — Incident Response Plan
DORA (Digital Operational Resilience Act) – Third-Party ICT Dependency Risk and Resilience
Control ID: Article 9 — ICT Security Policies and Article 10 — ICT-Related Incident Management
CISA Zero Trust Maturity Model 2.0 – Software Composition Analysis and Dependency Integrity
Control ID: Application Pillar — Application Security (Visibility & Analytics)
NIS2 Directive – Vulnerability Handling and Supply Chain Security
Control ID: Article 21 — Cybersecurity Risk Management Measures
ISO/IEC 27001:2022 – Technical Vulnerability Management and Third-Party Software Component Control
Control ID: Annex A 8.8 — Management of Technical Vulnerabilities and A 8.30 — Outsourced Development
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
PHP's CVE-2026-111497 Brotli memory corruption RCE directly threatens software teams using Guzzle HTTP defaults, exposing Windows builds to supply chain compromise via crafted compressed HTTP responses.
Information Technology/IT
IT infrastructure running PHP 8.2–8.5 on Windows with cURL auto-decompression enabled faces Critical CVSS 9.2 RCE risk, demanding immediate patching and egress traffic controls per NIST.800-53.SC-7.
Financial Services
PHP-driven financial applications processing HTTP responses risk memory corruption RCE exploitation; PCI.4.0.6.4.1 and Zero Trust Segmentation controls are critical to contain lateral movement post-compromise.
Health Care / Life Sciences
Healthcare platforms using PHP with Guzzle defaults face HIPAA.164.308(a)(1) compliance exposure; a Brotli-triggered RCE could enable data exfiltration of protected health information across hybrid cloud environments.
Sources
- PHP Issues Second Windows Security Update in Five Days to Fix Brotli Code Execution Flawhttps://thehackernews.com/2026/10/php-issues-second-windows-security.htmlVerified
- PHP Official Announcement: Updated PHP Windows Builds for Brotli Security Fixhttps://www.php.net/archive/2026.php#2026-10-26-1Verified
- PHP Foundation Discourse: Announce Updated PHP Windows Builds for Brotli Security Fixhttps://discourse.thephp.foundation/t/announce-updated-php-windows-builds-for-brotli-security-fix/6324Verified
- Google Brotli v1.2.1 Release Noteshttps://github.com/google/brotli/releases/tag/v1.2.1Verified
- Red Hat Security Advisory: CVE-2026-111497https://access.redhat.com/security/cve/CVE-2026-111497Verified
- CISA Known Exploited Vulnerabilities Cataloghttps://www.cisa.gov/known-exploited-vulnerabilities-catalogVerified
- PHP Downloads Page (Windows Builds)https://www.php.net/downloads.php?os=windowsVerified
- OpenAI Brotli Vulnerability Mitigation Guidancehttps://patchtheplanet.org/brotliVerified
- PHP Issues Emergency Patches for Two PHP2Shell Remote Code Execution Flawshttps://thehackernews.com/2026/10/php-issues-emergency-patches-for-two.htmlVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF is directly relevant here because the attacker's progression from initial PHP process compromise through lateral movement, C2 establishment, and data exfiltration all depend on unrestricted east-west reachability and permissive outbound paths that Zero Trust segmentation would likely constrain. By enforcing workload-level segmentation and identity-aware egress policy, CNSF would reduce the attacker's ability to expand beyond the initially compromised PHP host.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Inbound reachability to the PHP workload from untrusted or unexpected network origins could be reduced, limiting the attacker's ability to deliver the malicious Brotli payload through unanticipated external paths.
Control: Zero Trust Segmentation
Mitigation: Zero Trust segmentation would likely constrain the blast radius of the compromised PHP process by limiting its network-level access to adjacent workloads and internal services, even if local privilege escalation on the host itself succeeds.
Control: East-West Traffic Security
Mitigation: East-west traffic enforcement would likely reduce the attacker's ability to pivot freely from the compromised PHP host to adjacent workloads, constraining reachability to only explicitly permitted internal paths.
Control: Multicloud Visibility & Control
Mitigation: Centralized multicloud traffic visibility would likely surface anomalous outbound connection patterns from the PHP workload, reducing the attacker's ability to maintain a persistent C2 channel without detection.
Control: Egress Security & Policy Enforcement
Mitigation: FQDN-based egress policy enforcement would likely constrain the attacker's ability to transfer sensitive data to unauthorized external destinations, reducing the scope of successful exfiltration from the compromised PHP environment.
The residual blast radius would likely be constrained to the initially compromised PHP host and any workloads within the same permitted segmentation zone, reducing the attacker's ability to cause widespread ransomware deployment, persistent backdoor installation across multiple systems, or broad supply chain artifact tampering.
Impact at a Glance
Affected Business Functions
- Web Application HTTP Request Processing
- PHP-Based API and Microservice Communication
- Software Supply Chain Integrity and Dependency Management
- Windows Server PHP Runtime Environments
Estimated downtime: 2 days
Estimated loss: N/A
No confirmed data exfiltration has been reported. However, exploitation of this memory corruption RCE vulnerability could expose arbitrary server-side data including environment variables, application secrets, database credentials, session tokens, and any data processed by the affected PHP application. Organizations running PHP on Windows with Guzzle default settings or CURLOPT_ENCODING enabled are at elevated risk of full server compromise if a threat actor delivers a crafted Brotli-compressed HTTP response. The attack surface includes any outbound HTTP request made by the PHP application to an attacker-controlled or compromised server.
Recommended Actions
Key Takeaways & Next Steps
- • Immediately update all PHP Windows installations to the rebuilt packages (8.5.12-1, 8.4.27-1, 8.3.36-1, 8.2.35-1) that bundle Brotli 1.2.1, and validate the correct build using the -1 filename suffix and SHA-256 hash published on the PHP downloads page; as a temporary workaround, set Guzzle's decode_content option to false and avoid setting CURLOPT_ENCODING until patching is complete.
- • Deploy Inline IPS (Suricata-based) inspection on inbound and outbound HTTP/S traffic paths used by PHP applications to detect known exploit signatures matching CVE-2026-111497 malformed Brotli payload patterns before they reach vulnerable decompression code.
- • Enforce Egress Security and Policy controls (FQDN filtering, outbound firewall rules via Cloud Firewall/ACF) on all workloads hosting PHP services to prevent unauthorized outbound C2 connections and data exfiltration channels that would be established post-exploitation.
- • Apply Zero Trust Segmentation and East-West Traffic Security policies to restrict PHP application hosts from initiating lateral connections to internal databases, credential stores, or adjacent services beyond explicitly required flows, limiting blast radius if RCE is achieved.
- • Enable Multicloud Visibility and Threat Detection capabilities to baseline normal outbound HTTP decompression traffic patterns from PHP workloads and alert on anomalous compressed-response volumes, unexpected external server contacts, or sudden spikes in outbound data transfer indicative of active exploitation or exfiltration.



