CVE-2026-128017 in FrankenPHPinfo

Summary

by MITRE • 11/13/2026

FrankenPHP before 1.13.4 contains a double free vulnerability in worker mode that frees SG(request_info).content_type_dup twice when a worker script ends its loop after a non-form POST request. Unauthenticated attackers can send repeated JSON POST requests until the worker loop ends, aborting the whole process when USE_ZEND_ALLOC=0 is set.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/13/2026

The vulnerability identified in FrankenPHP versions prior to 1.13.4 represents a critical memory management flaw within its SAPI worker mode implementation. This issue specifically manifests as a double free condition affecting the request information structure, particularly targeting the content_type_dup field. The root cause lies in the lifecycle management of PHP workers during high-concurrency scenarios involving non-form POST requests. When a worker script processes such requests and subsequently terminates its execution loop, the internal cleanup routines fail to properly track whether memory has already been released. Consequently, the system attempts to deallocate the content_type_dup pointer for a second time after it has already been freed by an earlier routine in the same request cycle. This type of error is classified under CWE-415, which defines double free as a condition where a program frees a block of memory that has already been freed, leading to undefined behavior and potential system instability.

From an operational perspective, this vulnerability allows unauthenticated attackers to trigger denial-of-service conditions against the web server infrastructure. By sending repeated JSON POST requests, an attacker can force the worker process into a state where it repeatedly encounters the flawed code path upon loop termination. The severity of the impact is significantly amplified when the environment variable USE_ZEND_ALLOC is set to zero, which disables Zend's default memory allocator and relies on alternative allocation strategies that are more sensitive to such corruption. In these configurations, triggering the double free results in immediate process abortion or crash. This effectively removes available worker processes from the pool, reducing the server's capacity to handle legitimate traffic. If an attacker can sustain this pattern of requests across multiple workers, it can lead to a complete service outage as all background processing threads are terminated unexpectedly.

The exploitation vector for this vulnerability is straightforward and does not require authentication or prior access privileges. The attack relies on standard HTTP POST methods with JSON payloads, which are common in modern web applications and API interactions. This makes the vulnerability particularly dangerous because it can be triggered by any external entity capable of sending network requests to the FrankenPHP instance. The ATT&CK framework categorizes this type of activity under T1499, Endpoint Denial of Service, specifically noting techniques that exploit software vulnerabilities to disrupt service availability. Furthermore, the memory corruption aspect aligns with CWE-787, out-of-bounds write, as double frees often corrupt heap metadata structures used by allocators like ptmalloc or jemalloc, which can sometimes be leveraged for further exploitation beyond simple denial of service if the allocator state is sufficiently corrupted to allow arbitrary code execution.

Mitigation strategies must focus on immediate version upgrades and configuration hardening. The primary remediation step is to upgrade FrankenPHP to version 1.13.4 or later, where this double free logic has been corrected in the worker lifecycle management routines. For environments that cannot immediately patch due to dependency constraints, disabling USE_ZEND_ALLOC=0 may reduce the likelihood of immediate crashes, although it does not eliminate the underlying memory corruption risk entirely and is generally discouraged for production stability. Additionally, implementing rate limiting on POST endpoints can help mitigate the volume of requests an attacker can send before detection mechanisms trigger. Network-level controls such as Web Application Firewalls should be configured to monitor for abnormal patterns of JSON POST traffic that result in frequent worker restarts or error logs indicating memory allocation failures. Regular monitoring of server stability and worker process counts is essential to detect potential exploitation attempts early, allowing administrators to isolate affected nodes before a widespread denial-of-service event occurs.

Responsible

VulnCheck

Reservation

11/12/2026

Disclosure

11/13/2026

Moderation

accepted

CPE

ready

EPSS

0.00519

KEV

no

Activities

very low

Sources

Do you need the next level of professionalism?

Upgrade your account now!