Hacker News User Admits Early PHP Vulnerability Leak
A community member explains their rationale for sharing critical security details before the official disclosure window closed.
By Priya Marino ·

petecooper, a self-employed consultant and the solo founder of a mental health non-profit, has issued a public apology after revealing details of two critical PHP security flaws ahead of a scheduled embargo. The user stated they shared the Common Vulnerabilities and Exposures identifiers to alert the community about the urgency of the situation, claiming they had no knowledge of a formal restriction on sharing the information at that time. They emphasized that they held no official affiliation with the organizations involved in the disclosure process.
The early release of information concerns two remote code execution vulnerabilities, tracked as CVE-2026-109618 and CVE-2026-109619. In their written statement, petecooper acknowledged the significant impact their post had on the coordinated disclosure schedule. They noted that the action created additional workload for the teams involved and expressed sincere regret. The user accepted full responsibility for the timing of the post, explaining that their contact had informed them no embargo existed, a claim that was supposedly backed by that contact's own source.
Both bugs carry a severity score of 9.2, making them high-risk issues for developers. The PHP Foundation had intended to manage the public release in a controlled manner. This approach was designed to give website owners and application developers sufficient time to apply necessary patches before the flaws became widely known. However, the embargo did not reach all parties who received the advance warning, causing the news to spread faster than the foundation anticipated.
The leak from petecooper was not the only factor that disrupted the timeline. Several other leaks had already appeared on social media and other platforms prior to the official statement. These additional disclosures forced the PHP Foundation to move its announcement forward by one day. The organization also identified Chainguard as another entity that broke the embargo, revealing the information more than six hours before the planned date.
Dan Lorenc, the co-founder and chief executive officer of Chainguard, defended his company's decision on LinkedIn. He explained that he made the choice after consulting with several other researchers. Lorenc stated that once the fix became publicly available, he prioritized notifying the broader group of researchers rather than limiting the communication to only the company's customers.
The underlying issues are bugs located in the core PHP runtime. Researchers discovered these flaws using artificial intelligence tools, although they were not caused by rogue AI systems attacking the code. The use of such tools suggests that both security experts and malicious actors may now uncover vulnerabilities that have existed in widely used software for years or even decades. This dynamic turns each discovery into a race to develop and deploy fixes before the flaws can be exploited.
The situation highlights the complexities of coordinating security disclosures in a fast-moving digital landscape. As AI tools become more integrated into the process of finding software bugs, the window between discovery and public knowledge may continue to shrink. This places greater pressure on developers and organizations to maintain robust patching processes and clear communication channels.






