A newly disclosed high-severity vulnerability in PHP, tracked as CVE-2026-12184, poses a significant risk to web applications by allowing a remotely triggerable denial-of-service (DoS) condition.
This vulnerability can cause entire PHP-FPM process pools to crash. Details of the issue are outlined in the GitHub advisory GHSA-mhmq-mmqj-2v39. It affects multiple supported PHP branches, including versions before 8.3.32, 8.4.21, and 8.5.6.
PHP TLS Flaw
The flaw lies in the HTTP stream-handling logic, specifically in the php_stream_url_wrap_http_ex function.
According to the advisory, the vulnerability is triggered when Transport Layer Security (TLS) initialization fails during outbound connections. This failure can occur due to expired certificates or peer name validation errors.
When TLS setup fails via php_stream_xport_crypto_setup or php_stream_xport_crypto_enable, the stream resource is properly closed and reset to NULL. However, a subsequent cleanup routine incorrectly assumes the stream remains valid and attempts to reset the peer name unconditionally.
This logic flaw introduces a use-after-free–style condition, ultimately leading to process instability and a crash. Importantly, exploitation does not require specially crafted payloads or complex attack chains. Instead, a malicious or misconfigured remote server can present an invalid TLS configuration to trigger the failure condition.
As demonstrated in public issue discussions, this makes the vulnerability particularly dangerous in real-world environments where PHP applications frequently initiate outbound HTTPS requests.
The impact is significant in PHP-FPM deployments, where a single crash can terminate the entire worker pool, resulting in complete service disruption. Given PHP-FPM’s widespread use in high-traffic web applications, this creates a viable attack vector for remote attackers to crash services and cause sustained downtime repeatedly.
The vulnerability was identified by security researcher ndossche using a hybrid static-dynamic analysis tool, highlighting the growing effectiveness of automated vulnerability discovery techniques in uncovering subtle memory and logic issues in mature codebases.
PHP maintainers have addressed the issue through a patch released under pull request #21031. Users are strongly advised to upgrade immediately to the patched versions of PHP 8.3.32, 8.4.21, or 8.5.6. No workarounds have been officially documented, making patching the primary mitigation strategy.
In parallel, another moderate-severity vulnerability (CVE-2026-14355) has also been patched in PHP’s OpenSSL extension.
This issue involves memory corruption in the openssl_encrypt function when using the AES-WRAP-PAD algorithm, due to improper buffer sizing that fails to account for the RFC 5649 padding requirements. While exploitation is considered more complex, it may still result in application crashes and limited DoS scenarios.
Security teams should prioritize patching internet-facing PHP deployments and review application behavior involving outbound TLS connections. Monitoring for abnormal FPM crashes or repeated worker restarts may also help detect potential exploitation attempts.
The disclosure underscores the critical importance of robust error handling in cryptographic operations, particularly in widely deployed server-side runtimes like PHP.
Interact with Cyber Threats in Windows, Linux, macOS VMs to Trigger Full Attack Chain - Analyse Malware & Phishing with ANY RUN





