NULL pointer reset in PHP HTTP stream TLS failure path causes DoS
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Attack requirements
- Present
- Impact type
- —
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · GHSA-mhmq-mmqj-2v39. Fix status from GitHub.
Summary
PHP (php-src) fails to handle a failed TLS setup when fetching a URL over HTTP. When TLS crypto setup fails, for example because the peer name cannot be validated or the certificate has expired, the stream is closed and then reset to NULL, but a later cleanup step still tries to reset the peer name. A remote server can trigger this condition and crash the PHP-FPM process along with all its workers, causing a denial of service. The CVSS 4.0 vector indicates network attack with no privileges or user interaction and high availability impact.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Summary In `php_stream_url_wrap_http_ex`, when TLS crypto setup fails (via `php_stream_xport_crypto_setup` or `php_stream_xport_crypto_enable`), the stream is closed and reset to `NULL`. However, the subsequent peer name cleanup block unconditionally tries to reset the peer name. This is triggerable via a failure to validate the peer name or an expired certificate. As demonstrated by https://github.com/php/php-src/issues/21468 this is triggerable without requiring specially-crafted code, and with a remote server. ### Details Patch available via https://github.com/php/php-src/pull/21031 ### Impact The impact is a remotely-triggerable DoS bringing the entire fpm process down with all its workers. ### Additional Information This was first discovered by a hybrid static-dynamic analyzer I'm developing.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | php-src | < 8.3.32 | 8.3.32 | Patch available | GHSA-mhmq-mmqj-2v39 |
| — | php-src | < 8.4.21 | 8.4.21 | Patch available | GHSA-mhmq-mmqj-2v39 |
| — | php-src | < 8.5.6 | 8.5.6 | Patch available | GHSA-mhmq-mmqj-2v39 |
- php-src Vendor— Affected < 8.3.32 Fixed in 8.3.32 Patch available GHSA-mhmq-mmqj-2v39
- php-src Vendor— Affected < 8.4.21 Fixed in 8.4.21 Patch available GHSA-mhmq-mmqj-2v39
- php-src Vendor— Affected < 8.5.6 Fixed in 8.5.6 Patch available GHSA-mhmq-mmqj-2v39
Remediation
Upgrade php-src to 8.3.32, 8.4.21 or 8.5.6, which fix the issue. The sources do not list a vendor advisory for this fix.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-mhmq-mmqj-2v39 php-src Fixed in 8.3.32 Advisory →
- Fix · GHSA-mhmq-mmqj-2v39 php-src Fixed in 8.4.21 Advisory →
- Fix · GHSA-mhmq-mmqj-2v39 php-src Fixed in 8.5.6 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-mhmq-mmqj-2v39
- 2026-11-12 Alias added: CVE-2026-12184
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences