{"id":810047,"date":"2026-10-22T06:02:10","date_gmt":"2026-10-22T06:02:10","guid":{"rendered":"https:\/\/www.newsbeep.com\/uk\/810047\/"},"modified":"2026-10-22T06:02:10","modified_gmt":"2026-10-22T06:02:10","slug":"php-blames-supply-chain-security-biz-chainguard-for-putting-huge-chunks-of-the-web-at-risk","status":"publish","type":"post","link":"https:\/\/www.newsbeep.com\/uk\/810047\/","title":{"rendered":"PHP blames supply chain security biz Chainguard for putting huge chunks of the web at risk"},"content":{"rendered":"<p>PHP developers have accused software supply chain security shop Chainguard of effectively revealing critical bugs in the open-source scripting language ahead of a planned official disclosure.<\/p>\n<p>On Wednesday, just hours after <a href=\"https:\/\/www.theregister.com\/security\/2026\/10\/21\/php-devs-publish-critical-bug-fix-as-site-owners-warned-pull-em-offline-if-youre-unpatched\/5304519\" target=\"_blank\" rel=\"nofollow noopener\">releasing emergency patches<\/a> for the two bugs collectively called PHP2shell, PHP maintainers published a blog about how the vulnerabilities were found and fixed.<\/p>\n<p>They credited researchers at Calif, OpenAI, and Wiz with finding the security holes between August and September. All three companies have said they used AI models to find the vulnerabilities, which are now tracked as CVE-2026-109618 and CVE-2026-109619, and can allow an unauthenticated attacker to execute code on servers running PHP.\u00a0<\/p>\n<p>This is especially serious because PHP powers huge chunks of the public web. It also adds a dose of irony to the \u201cleak and disrupted disclosure\u201d part of the blog, which <a href=\"https:\/\/thephp.foundation\/blog\/2026\/10\/21\/todays-php-security-release-and-how-were-strengthening-php-security\/\" target=\"_blank\" rel=\"nofollow noopener\">blames Chainguard<\/a> &#8211; a company that aims to secure software supply chains by hardening open source code &#8211; for the messy disclosure.<\/p>\n<p>The trouble, according to PHP developers, started on Tuesday around 15:00 UTC, when \u201ctwo CVE IDs began circulating on online forums and social media,\u201d along with incorrect information about the release time and CVSS severity rating. At that point, no technical details leaked. <\/p>\n<p>The rumors, however, prompted PHP maintainers to <a href=\"https:\/\/www.php.net\/archive\/2026.php#2026-10-20-1\" target=\"_blank\" rel=\"nofollow noopener\">warn people in advance<\/a> about the critical flaws, and move the planned disclosure forward a day, from Thursday to Wednesday.<\/p>\n<p>\u201cDistributors were still packaging the fix, so releasing immediately would have left many users without an easy way to update,\u201d the PHP Foundation blog says. \u201cMoving the release forward by one day was the best compromise between acting quickly, giving people time to prepare, and making sure everyone had a simple update path when the vulnerabilities were disclosed.\u201d<\/p>\n<p>A couple of hours later, Calif \u201cmistakenly\u201d published a video showing a proof-of-concept exploit and \u201cadditional, though limited\u201d information about the bugs, we\u2019re told.\u00a0<\/p>\n<p>\u201cMitigation advice we started providing to a few critical infrastructure providers around Oct 20th 23:00 UTC, may have leaked as well,\u201d the PHP blog says, but it does not name these providers. And then it throws Chainguard under the bus:<\/p>\n<p class=\"quote\">\u201cOn October 21st at 07:41 UTC, more than six hours before the coordinated release, Chainguard unilaterally broke the embargo and published built images containing the fix. Like other distributors, Chainguard had received the patch in advance so its users could update the moment the vulnerabilities were disclosed. Any attacker could now study the fix in binary form while every other PHP user was still waiting for the release. This disregarded weeks of work by many parties toward a coordinated disclosure.\u201d<\/p>\n<p>Chainguard CEO: &#8216;We made the call&#8217;<\/p>\n<p>Chainguard CEO Dan Lorenc spoke with The Register on Wednesday, and while he doesn\u2019t dispute the timeline, said his company &#8220;didn&#8217;t leak.&#8221;<\/p>\n<p> \u201cThese things are messy,\u201d Lorenc said.<\/p>\n<p>Chainguard learned \u201csomething was coming in PHP\u201d on Friday from one of the researchers that found the bugs, Lorenc told us. Later that night, using his company\u2019s AI harness and a frontier model, the CEO and the Chainguard team independently found the same memory corruption vulnerabilities.<\/p>\n<p>All it took was a \u201cbasic prompt of \u2018find bad vulnerabilities in PHP,\u2019\u201d Lorenc <a href=\"https:\/\/www.linkedin.com\/feed\/update\/urn:li:activity:7518756994284077056\/\" target=\"_blank\" rel=\"nofollow noopener\">wrote<\/a> in a subsequent LinkedIn post.<\/p>\n<p>On Saturday, Chainguard began working with the PHP maintainers, confirmed that some of its findings matched the bug reports, and helped test the patches.<\/p>\n<p>\u201cThe patches are crazy &#8211; this is not a simple vulnerability,\u201d Lorenc told The Register. \u201cIt really did take them months to build a real, working patch for it. And then on Monday, the rumors started, and yesterday it just spiraled.\u201d<\/p>\n<p>Some people published POCs on social media, other security vendors reported seeing real-world exploitation, and late Tuesday night Lorenc told us he decided to ship the fixes, and notified the PHP coordinated disclosure channel about his plans.<\/p>\n<p>\u201cPeople were getting hit in advance\u201d of the official PHP disclosure, \u201cso we made the call to ship the fixes under that,\u201d Lorenc said. \u201cIt&#8217;s coordinated vulnerability disclosure, unless there&#8217;s evidence of active exploits in the wild.\u201d\u00a0<\/p>\n<p>Also on Tuesday night, Chainguard published built artifacts and made them accessible to anyone, not just customers. \u201cAnd then I woke up this morning and saw that this was all our fault,\u201d Lorenc said.<\/p>\n<p>When asked if he would do anything differently, given the fallout from Chainguard\u2019s early disclosure, Lorenc said no. \u201cThis process and policy is based on trying to coordinate as much as possible until shit hits the fan and people start weaponizing things,\u201d he said. \u201cIt sucks, because we really are all on one team, and there&#8217;s bad guys over there doing stuff.\u201d<\/p>\n<p>Chainguard\u2019s honeypots trapped IPs from China and Russia targeting the vulnerabilities on Wednesday, Lorenc added.\u00a0<\/p>\n<p>\u201cJust being told there&#8217;s a vulnerability in a piece of software &#8211; even something as big as PHP &#8211; is enough to find it,\u201d he told us. \u201cI did that myself without any other knowledge on Friday.&#8221;<\/p>\n<p>&#8220;I think this is kind of the new normal. People are able to build an exploit in hours without even knowing what the vulnerability is.&#8221;<\/p>\n<p>What we know about the CVEs and how to exploit them<\/p>\n<p>While we still don\u2019t know the scope of exploitation &#8211; or what will happen to vulnerable legacy systems that don\u2019t have security fixes &#8211; threat hunters predict it\u2019s going to be a doozy.<\/p>\n<p>\u201cSuccessful exploitation could allow attackers to take control of affected servers, steal sensitive data, and deface the websites running on them,\u201d Wiz researchers Sagi Tzadik, Shir Tamari, Nir Ohfeld, and Tomer Schwartz warned on Wednesday, adding the oft-quoted stat that PHP powers 70 percent of all websites in the world.<\/p>\n<p>\u201cEvery PHP version released in the last decade is affected by at least one of these vulnerabilities, going back to version 5.4,\u201d the Wiz kids wrote. \u201cAttackers can exploit them remotely, in some cases fairly easily. Immediate patching is strongly advised.\u201d<\/p>\n<p>Both bugs are related to how PHP handles memory management and error handling, and both lead to remote code execution (RCE). They can cause a corrupted internal PHP state when a request ends unexpectedly, and then a later request can reuse that state, leading to memory disclosure or RCE.\u00a0<\/p>\n<p>\u201cBoth are memory corruption vulnerabilities,\u201d VulnCheck researcher Patrick Garrity explained. \u201cIf an attacker can shape the memory PHP trusts, they can potentially hijack what it does next, and in these cases that means remote code execution.\u201d<\/p>\n<p>CVE-2026-109618 (<a href=\"https:\/\/github.com\/php\/php-src\/security\/advisories\/GHSA-w8hw-w9fx-j79w\" target=\"_blank\" rel=\"nofollow noopener\">GHSA-w8hw-w9fx-j79w<\/a>) leads to RCE via out-of-memory corruption. \u201cIf a request reached PHP&#8217;s memory_limit at exactly the wrong moment, PHP could leave partially initialized internal data behind and later treat it as valid, corrupting memory,\u201d the project maintainer wrote. \u201cOn Apache with mod_php, an unauthenticated request can trigger this before any application code runs.\u201d<\/p>\n<p>CVE-2026-109619 (<a href=\"https:\/\/github.com\/php\/php-src\/security\/advisories\/GHSA-6wmf-4rv5-p3rp\" target=\"_blank\" rel=\"nofollow noopener\">GHSA-6wmf-4rv5-p3rp<\/a>) allows RCE via stale state. \u201cA fatal error at the wrong point could leave internal state pointing to memory that belonged to a previous request,\u201d according to the PGP Foundation. \u201cA later request handled by the same worker could then use that freed memory. A use-after-free and worker crash were confirmed, and the reporter demonstrated remote code execution against a real-world application running on Apache with mod_php.\u201d\u00ae<\/p>\n","protected":false},"excerpt":{"rendered":"PHP developers have accused software supply chain security shop Chainguard of effectively revealing critical bugs in the open-source&hellip;\n","protected":false},"author":2,"featured_media":810048,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[84,59,56,54,55],"class_list":["post-810047","post","type-post","status-publish","format-standard","has-post-thumbnail","category-business","tag-business","tag-gb","tag-uk","tag-united-kingdom","tag-unitedkingdom"],"_links":{"self":[{"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/posts\/810047","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/comments?post=810047"}],"version-history":[{"count":0,"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/posts\/810047\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/media\/810048"}],"wp:attachment":[{"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/media?parent=810047"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/categories?post=810047"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/tags?post=810047"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}