{"id":183958,"date":"2026-10-22T17:40:23","date_gmt":"2026-10-22T15:40:23","guid":{"rendered":"https:\/\/prohoster.info\/blog\/news\/narusheniya-embargo-i-zatyagivanie-razrabotki-patchej-v-hode-ustraneniya-uyazvimostej-v-php"},"modified":"2026-10-22T17:40:28","modified_gmt":"2026-10-22T15:40:28","slug":"embargo-violations-and-patch-development-delays-in-php-vulnerability-remediation","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/embargo-violations-and-patch-development-delays-in-php-vulnerability-remediation","title":{"rendered":"Embargo violations and delays in patch development occurred during the resolution of vulnerabilities in PHP.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
PHP developers released a report on the issues that arose during the resolution of the critical vulnerabilities in PHP that were addressed yesterday. Information about the vulnerability related to memory exhaustion was obtained during an external audit back in 2024, but it was only regarded as a theoretical possibility for an attack. Fixing it was delayed due to disagreements among PHP developers on how to resolve the vulnerability. Several competing proposals were considered, each with its downsides. A choice had to be made between breaking backward compatibility, introducing new attack vectors leading to denial of service, and the necessity of making changes to numerous third-party extensions. <\/p>\n
A few months ago, the companies Calif and Wiz independently discovered viable exploit methods for the vulnerability using AI models GPT-5.6 and Gemini 4 Argon. They informed the PHP developers about this on August 11 and 24, 2026. Following this, the development of fixes was given the highest priority, and the decision-making process was reformed to allow for more prompt responses concerning complex trade-offs (such decisions can now be made by majority vote without requiring strict consensus).<\/p>\n
Initially, in coordination with the distributions, the date for the release of the fix was set for October 22, but it was later moved to October 21 after a leak on October 20 on social media regarding CVE identifiers and incorrect data about the timing of the upcoming patch releases. <\/p>\n
Shortly after the announcement of the upcoming fixes, Calif, which identified one of the vulnerabilities, mistakenly published a video demonstrating the exploit, revealing some details that could narrow down the search area and recreate information about the issue. The video was quickly deleted, which only fueled researchers' desire to dig into the vulnerability and accelerated work on alternative exploit prototypes. <\/p>\n
In addition, six hours before the scheduled release of the fixes, Chainguard breached the embargo and published builds of its distribution containing the corrected version of PHP. This violation allowed malicious actors to study the fix before the official release and undermined all efforts for coordinated disclosure and simultaneous publication of fixes across different distributions.<\/p>\n
Supplement: Sixteen hours after the details of the vulnerabilities of the universal exploit were disclosed, no mass attacks have been observed yet, which is explained by the complexity of exploiting the vulnerability due to the need to determine the layout of structures in the process's memory, which is specific to each build. The published working exploit prototypes are tied to specific configurations and conducting attacks under laboratory conditions. Additionally, many fake exploits have appeared, which are AI hallucinations, merely creating the appearance of an attack tied to configuration errors or only working in the presence of other critical vulnerabilities. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"