In 30 seconds
A proof of concept for CVE-2026-129496 is now public. On November 20, 2026, an advisory entry on dbu.gs, a GitHub repository named php-tzcache-rce, and an announcement from the ptdbugs account on X all surfaced with the same timestamp, pointing to exploit code for a use-after-free in PHP's timezone cache. A use-after-free, in plain terms, is a bug where the program keeps using memory it has already handed back.dbu.gsdbu.gs · rssOpen original sourceSee in source listgithub.comgithub.com · rssOpen original sourceSee in source listptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
According to the advisory, the flaw lets an unauthenticated remote attacker crash PHP-FPM, Apache mod_php or CGI workers with a single crafted request, and arbitrary code execution may be possible, a path the source says was demonstrated using known memory addresses. PHP versions before 8.2.36, and the 8.3, 8.4 and 8.5 lines before 8.3.37, 8.4.28 and 8.5.13 respectively, are listed as affected.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
What happened
The public trail starts with three artifacts that share one publication timestamp: the advisory entry PT-2026-151600 on dbu.gs, the GitHub repository abraxas/php-tzcache-rce holding the proof of concept, and a post from ptdbugs on X announcing that a PoC or exploit 'has been discovered' for CVE-2026-129496, with vendor listed as PHP Group and product as PHP.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listgithub.comgithub.com · rssOpen original sourceSee in source list
The advisory describes a two-step failure. In non-thread-safe builds, a diagnostic written to a file-based error_log during module startup, for example an invalid date.timezone value or a session configuration warning, makes the timezone cache live in startup memory that is later freed even though a reference to it survives. Then a diagnostic raised early in a worker's first request, such as the max_input_vars warning, reaches for that freed cache and the worker goes down.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
Why it matters
The advisory stresses that the attacker needs no account and no login, just a crafted request, and that the blast radius covers three of the most common ways PHP is served: PHP-FPM, Apache mod_php and CGI. At minimum, that is a remote denial of service that can be repeated against worker after worker.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
If the code execution claim holds beyond the lab demonstration, the stakes jump from downtime to full server takeover, since PHP workers run with the site's own privileges. Nothing in the current evidence shows that final step working in the wild, so the conservative read is to treat the crash capability as credible and the code execution claim as still unproven.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
What to do
The advisory's fix line is straightforward: move to PHP 8.2.36, 8.3.37, 8.4.28 or 8.5.13, the first releases listed as patched in each affected branch.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
For servers that cannot upgrade immediately, the described trigger suggests a stopgap: make sure nothing is written to a file-based error_log during startup. Correcting an invalid date.timezone value and any session configuration warnings removes the precondition the bug needs. This workaround follows from the advisory's own description of the mechanism rather than from a separately sanctioned vendor recommendation.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
Confirmed and still uncertain
What the advisory puts on the table: the flaw is a timezone cache use-after-free, it affects PHP before 8.2.36, 8.3.37, 8.4.28 and 8.5.13 in their respective lines, an unauthenticated crafted request can crash workers in three deployment modes, and code execution 'may be possible' with a demonstration that relied on known memory addresses.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
What stays open: whether the code execution path works reliably outside a controlled memory layout, whether any real attacks have used the PoC, since this batch contains no sign of that, which distributions have already shipped the patched builds, and what the repository's code actually does, because its contents were not retrieved here.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listgithub.comgithub.com · rssOpen original sourceSee in source list
What people are saying
The loudest voice so far is ptdbugs on X, which announced the PoC and carried the full technical description, framing the find as a case where a 'timezone cache use-after-free can lead to remote code execution' and linking both the advisory and the code repository.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
The proof of concept itself sits under the GitHub account abraxas. No statement from the PHP Group or from distribution security teams appears in this batch, so the technical narrative currently rests on the advisory page and the account that announced it, and should be read as their account of the bug rather than independent confirmation.github.comgithub.com · rssOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list
Evolution
This story has no arc yet because everything landed at once. The advisory page, the GitHub repository and the X announcement all carry the same timestamp of November 20, 2026, so what exists today is the initial drop of advisory plus exploit code, not a developing thread with earlier reports or vendor back-and-forth to reconstruct.dbu.gsdbu.gs · rssOpen original sourceSee in source listgithub.comgithub.com · rssOpen original sourceSee in source listptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
Reach
2 independent groups, 1 updates, and 3 engagements.
Technical detail
The mechanism, as described, is narrow and configuration-dependent. It requires a non-thread-safe build and a deployment where startup diagnostics go to a file-based error_log, with an invalid date.timezone value or a session configuration warning given as examples. That early write allocates the timezone cache in startup memory which the runtime later frees while keeping a dangling reference to it, the classic setup for a use-after-free.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
The crash arrives when a worker handles its first request and raises an early diagnostic, the max_input_vars warning being the named example, which then touches the freed cache. From there the advisory reports worker crashes across PHP-FPM, Apache mod_php and CGI, and says arbitrary code execution may be possible with a demonstration that assumed known memory addresses, meaning the harder problem of locating code and data in a randomized memory layout was sidestepped in the demo rather than solved.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listgithub.comgithub.com · rssOpen original sourceSee in source list
Sources and evidence
This item rests on three artifacts: the dbu.gs advisory entry for PT-2026-151600, the GitHub repository abraxas/php-tzcache-rce hosting the proof of concept, and the ptdbugs post on X that carried the full description of CVE-2026-129496, including affected versions and the triggering conditions.dbu.gsdbu.gs · rssOpen original sourceSee in source listgithub.comgithub.com · rssOpen original sourceSee in source listptdbugsx.com · ptdbugs · xOpen original sourceSee in source list
Read them with the usual caution. The advisory body and the repository contents were not retrieved in this batch, so every technical claim here travels through the X summary of the advisory, and no php.net release note or independent researcher write-up is included to corroborate the versions, the mechanism or the exploitability claims.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list
Sources
- dbu.gsdbu.gs · rss
- github.comgithub.com · rss
- ptdbugsx.com · ptdbugs · x



