AdvertiseDonate
The stories that matter, every day.
Thursday, November 5, 2026
Breaking Review · 100 North 18th Street, Suite 300, Philadelphia, PA 19103

PHP Foundation Moves Patch Release Up After Early Leaks

A Hacker News post and a Chainguard notification forced the organization to announce fixes for two critical runtime bugs 24 hours ahead of schedule.

By Benjamin Bernard ·

Illustration for: PHP Foundation Moves Patch Release Up After Early Leaks
Illustration generated for this article, not a news photograph.

The PHP Foundation advanced its security patch release by one day on Thursday after details of two critical vulnerabilities leaked before the planned disclosure window closed. The organization moved the announcement from October 25 to October 24 to limit the exposure window for websites running the language.

The two flaws, tracked as CVE-2026-109618 and CVE-2026-109619, allow for remote code execution in the PHP runtime. Both carry a severity score of 9.2. Researchers discovered the bugs using AI tools, a method that can uncover vulnerabilities hidden in widely used code for years.

Hacker News user petecooper posted details of the flaws ahead of the embargo. In a public apology, the user said they shared the information to warn others following PHP's four-week release cycle that the issue was urgent. Petecooper described themselves as a self-employed consultant and the solo founder of a mental health non-profit. They stated they had no affiliation with the involved organizations and did not know an embargo existed.

Petecooper wrote, "I appreciate this has had considerable knock-on effects with the schedule for co-ordinated disclosure, and created additional workload. I am truly sorry. I take full responsibility for my actions." The user added that their contact had claimed there was no embargo, a statement that the contact's own source also made.

Chainguard also broke the embargo by more than six hours. Dan Lorenc, co-founder and CEO of Chainguard, defended the move on LinkedIn. He said he acted after consulting with other researchers and notified the wider group once the fix became public, rather than restricting the alert to company customers.

Some recipients of the advance warning failed to pass along the embargo instructions, causing information to spread faster than intended. The early leak forced the foundation to compress its timeline and push the public release forward by a full day.

Source: Tom's Hardware

More Tech · Report a business · Got a Story?

Get Breaking Review in your inboxThe stories that matter, every day. Free, a few times a week, unsubscribe any time.

Related stories

Get Breaking Review in your inboxThe stories that matter, every day. Free, a few times a week, unsubscribe any time.