← All stories
● Covered by 1 source · 1 reportMedium impact1 neutral

Chainguard Defends Early Release of Patched PHP Images Before Embargo Lifted

🔄 Updated 9d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Chainguard released patched PHP images early on October 21.
  • PHP maintainers accused Chainguard of giving attackers a head start.
  • Chainguard stated attackers were already exploiting or close to exploiting the bugs.
  • Vulnerabilities CVE-2026-109618 and CVE-2026-109619 allowed remote code execution.

Early Release of PHP Patches

Chainguard co-founder and CTO Matt Moore addressed the company's decision to release patched PHP container images ahead of a security embargo. The release occurred more than six hours before the agreed-upon coordinated security release on October 21.

Justification for Breaking Embargo

Moore stated that Chainguard 'owns the decision' to release early, asserting it was not done in a vacuum. The company's rationale was that security vendors had reported activity targeting the vulnerabilities, suggesting attackers were already aware of or actively exploiting the flaws. Chainguard believed attackers could already exploit the bugs or were close to doing so.

The PHP Vulnerabilities

The two vulnerabilities, CVE-2026-109618 (out-of-memory corruption) and CVE-2026-109619 (stale global state), are collectively known as PHP2Shell. These were serious memory-management and error-handling flaws in PHP itself. Under specific conditions, an unauthenticated attacker could execute code on a PHP server.

The first bug involved PHP's interruption during internal data setup when a memory limit was reached, leading to misinterpretation of unfinished data. The second involved PHP retaining references to freed memory after an error, allowing subsequent requests to access invalid memory. Both could lead to remote code execution within the server's PHP process.

Impact and Exploitation

Researchers demonstrated remote code execution for the first vulnerability through both Apache/mod_php and PHP-FPM paths. The second vulnerability was demonstrated against a real-world Apache/mod_php application. These were fundamental security holes within PHP, not issues resolvable by updating application-level components like WordPress plugins.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 21

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

Chainguard's CTO Matt Moore defended the company's decision to release patched PHP container images six hours before a coordinated security embargo lifted. The company argued that attackers were already targeting the vulnerabilities, making an early release necessary despite accusations from PHP maintainers.