PHP2Shell:修订间差异
无编辑摘要 |
外部链接语言标注改为纯文本 |
||
| (未显示同一用户的3个中间版本) | |||
| 第1行: | 第1行: | ||
| ⚫ | |||
{{Short description|2026 software security vulnerability}} |
|||
| title = PHP2Shell |
|||
{{Current|2=current cybersecurity incident|date=October 2026}} |
|||
| ⚫ | |||
{{Use Canadian English|date=October 2026}} |
|||
| caption = CaelLab 的 Phabricator 在漏洞修补前暂停服务的公告 |
|||
{{Use dmy dates|date=October 2026}} |
|||
| ⚫ | |||
| |
| label1 = 类型 |
||
| data1 = 计算机安全漏洞 |
|||
| ⚫ | |||
| label2 = CVE 编号 |
|||
| ⚫ | |||
| ⚫ | |||
| caption = [[CaelLab]]'s [[Phabricator]] instance as seen hours before the patch, having been disabled as a precaution |
|||
| label3 = CVSS 评分 |
|||
| discovered = {{Start date and age|df=yes|2026|8|1}} |
|||
| data3 = 9.2(CVSS 4.0,严重) |
|||
| patched = {{Start date and age|df=yes|2026|10|21}} |
|||
| label4 = 发现日期 |
|||
| discoverer = Calif, [[OpenAI]], [[Wiz, Inc.|Wiz]] |
|||
| |
| data4 = 2026年8月 |
||
| label5 = 公开日期 |
|||
| affected software = [[PHP]] versions 5.4–8.5<ref>{{cite web |title=PHP2Shell: AI uncovers critical RCE vulnerabilities affecting 70% of the Internet {{!}} Wiz Blog |url=https://www.wiz.io/blog/php2shell-php-rce |website=wiz.io |ref=Wiz |language=en-us |date=21 October 2026}}</ref> |
|||
| data5 = 2026年10月20日 |
|||
| label6 = 修补日期 |
|||
| data6 = 2026年10月21日 |
|||
| label7 = 发现者 |
|||
| data7 = Calif、OpenAI、Wiz |
|||
| label8 = 影响软件 |
|||
| data8 = PHP 5.4 至 8.5 |
|||
| label9 = 网站 |
|||
| data9 = [https://php2shell.com php2shell.com] |
|||
}} |
}} |
||
'''PHP2Shell''' 是 2026 年公开的两项 [[PHP]] 高危漏洞的合称,编号分别为 '''CVE-2026-109618''' 和 '''CVE-2026-109619'''。两者都是 PHP 解释器中的内存安全问题,影响 PHP 5.4 至 8.5 版本,可导致远程代码执行(RCE)。PHP 是使用最广泛的[[服务器]]端[[编程语言]]之一,这两项漏洞在公开时被认为可能影响[[全球]]约七成的网站。 |
|||
'''PHP2Shell''' is a pair of high-impact [[Vulnerability (computer security)|vulnerabilities]] ('''CVE-2026-109618'''<ref>{{cite web|url=https://www.cve.org/CVERecord?id=CVE-2026-109618|title=CVE-2026-109618|publisher=Mitre}}</ref> and '''CVE-2026-109619'''<ref>{{cite web|url=https://www.cve.org/CVERecord?id=CVE-2026-109619|title=CVE-2026-109619|publisher=Mitre}}</ref>) in [[PHP]] versions 5.4{{endash}}8.5 that allow [[Arbitrary code execution|remote code execution]] (RCE). Their existence was publicly announced on 20 October 2026.<ref name="oct20">{{Cite web |date=20 October 2026 |title=PHP: News Archive - 20 Oct 2026 |url=https://www.php.net/archive/2026.php#2026-10-20-1 |access-date=21 October 2026 |website=www.php.net |language=en}}</ref> An emergency [[Patch (computing)|patch]] for versions 8.2, 8.3, 8.4 and 8.5 and details about the vulnerabilities were released the following day.<ref name="oct21">{{Cite web |date=21 October 2026 |title=PHP: News Archive - 21 Oct 2026 |url=https://www.php.net/archive/2026.php#2026-10-21-5|access-date=21 October 2026 |website=www.php.net |language=en}}</ref> |
|||
漏洞由美国安全公司 Calif 的研究者借助[[人工智能]]发现,以色列与美国的云安全公司 Wiz 也独立发现了同样的问题。PHP 维护团队于 2026 年 10 月 20 日提前公布消息,次日在发布紧急补丁的同时公开了漏洞细节<ref name="oct20">{{cite web |title=PHP: News Archive - 20 Oct 2026 |url=https://www.php.net/archive/2026.php#2026-10-20-1 |website=www.php.net |date=2026-10-20 |access-date=2026-11-19 |language=en}}</ref><ref name="oct21">{{cite web |title=PHP: News Archive - 21 Oct 2026 |url=https://www.php.net/archive/2026.php#2026-10-21-5 |website=www.php.net |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref>。由于影响范围大,多国网络安全机构建议无法立即更新的机构将网站临时下线,[[维基]]媒体基金会、[[互联网]]档案馆等网站以及日本多家网络服务在修补期间暂停了服务<ref name="nbc">{{cite news |last=Collier |first=Kevin |title=Critical vulnerabilities in commonly used web code spark rush to update systems |url=https://www.nbcnews.com/tech/security/critical-vulnerabilities-php-update-systems-rcna604751 |work=NBC News |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref><ref name="reuters">{{cite news |last1=Satter |first1=Raphael |last2=Marchandon |first2=Leo |last3=Ghosh |first3=Kanjyik |last4=Pardesi |first4=Rajveer |title=Government websites go dark after AI-discovered flaw sparks security scramble |url=https://www.reuters.com/world/asia-pacific/eu-agency-warns-websites-may-need-be-taken-offline-php-prepares-patches-2026-10-21/ |work=Reuters |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref><ref name="itmedia">{{cite news |title=著名ITサービス相次いで緊急メンテへ コドモン、シャドバ、BASE、さくらのレンタルサーバなど 「PHP」脆弱性に起因か |url=https://www.itmedia.co.jp/news/article/2610/21/2000002472/ |work=ITmedia |date=2026-10-21 |access-date=2026-11-19 |language=ja}}</ref>。 |
|||
==Discovery== |
|||
PHP versions as early as 5.4 (released in 2012)<ref>{{Cite web |title=PHP: Releases |url=https://www.php.net/releases/index.php |access-date=22 October 2026 |website=www.php.net |language=en}}</ref> are affected by these vulnerabilities, and while concerns around [[memory safety]] bugs had been raised decades before, no action was taken at the time because it was not thought that developing a working [[Exploit (computer security)|exploit]] could be feasible.<ref name="Kan2026" /><ref name="McMillan2026" details="{{subref|q=The class of bugs had been hiding in PHP's source code for years. A security researcher had flagged it as a problem area decades earlier, but the flaw had been considered too difficult to exploit and was largely forgotten, Duong said.}}">{{cite news |last1=McMillan |first1=Robert |title=Exclusive {{!}} AI Just Found a Bug That Puts up to 70% of the World's Websites at Risk |url=https://www.wsj.com/tech/cybersecurity/ai-just-found-a-bug-that-puts-up-to-70-of-the-worlds-websites-at-risk-fd0902ea |url-access=subscription |access-date=21 October 2026 |work=Wall Street Journal |date=21 October 2026}}</ref> A PHP core developer discovered the [[Out of memory|out-of-memory]] error behind one of the vulnerabilities during an audit in 2024, but the [[Software bug|bug]] was never fixed; the development team could not reach consensus on how to do so and a specific exploit had not yet been discovered, so the issue was not prioritized.<ref name="Constantin2026">{{cite news |last1=Constantin |first1=Ana Maria |title=PHP knew about one of the flaws in 2024 but could not agree a fix |url=https://thenextweb.com/news/php-foundation-structural-failure-2024-flaw-leak |access-date=21 October 2026 |work=The Next Web |date=21 October 2026}}</ref><ref>{{Cite web |title=Today's PHP Security Release, and How We're Strengthening PHP Security |url=https://thephp.foundation/blog/2026/10/21/todays-php-security-release-and-how-were-strengthening-php-security/ |access-date=21 October 2026 |website=thephp.foundation |language=en}}</ref> |
|||
| ⚫ | |||
The vulnerabilities were independently discovered by two parties: Ryan Austin, a researcher at the [[California]]-based<ref>{{cite news |last1=Volz |first1=Dustin |title=A Hacking Tool Built With A.I. Can Breach Phones Without a Click |url=https://www.nytimes.com/2026/09/08/us/politics/calif-ai-worm-wechat-hack.html |access-date=21 October 2026 |work=The New York Times |date=8 September 2026}}</ref> security firm Calif, as part of the [[OpenAI]] "Patch the Planet" project in August 2026, and the Israeli–American cloud security company [[Wiz, Inc.|Wiz]], a subsidiary of [[Alphabet Inc.]] and a part of [[Google Cloud]].<ref name="McMillan2026" details="{{subref|q=Ryan Austin, a researcher at Calif, uncovered the flaws with help from GPT-5.6 Sol, one of OpenAI's most advanced models, during an audit of PHP's source code in August. ... Researchers from Google's Wiz cybersecurity team soon reached out with new exploits, which they had discovered independent of Calif. }}" /> Austin used OpenAI's [[GPT-5.6 Sol]] model to assist with finding the vulnerability.<ref name="McMillan2026" details="{{subref|q=Ryan Austin, a researcher at Calif, uncovered the flaws with help from GPT-5.6 Sol, one of OpenAI's most advanced models, during an audit of PHP's source code in August. ... Researchers from Google's Wiz cybersecurity team soon reached out with new exploits, which they had discovered independent of Calif. }}" /> Wiz researchers used the large language models [[Gemini (language model)|Gemini 4 Argon]] and GPT-5.6 Sol, as well as their own tool, Wiz Atlas, to help with their research.<ref name="Satter2026" /> |
|||
PHP 5.4 于 2012 年发布,这两项漏洞从那时起便存在于 PHP 的源代码中<ref name="phpreleases">{{cite web |title=PHP: Releases |url=https://www.php.net/releases/index.php |website=www.php.net |access-date=2026-11-19 |language=en}}</ref>。内存安全方面的问题在更早的时候就有人指出,但当时认为实际利用并不可行,因此没有采取行动<ref name="kan">{{cite news |last=Kan |first=Michael |title=This Flaw Is So Serious Websites Should Consider Going Offline, NSA Says |url=https://www.pcmag.com/news/php-flaw-is-so-serious-websites-should-consider-going-offline-nsa-says |work=PCMag |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref><ref name="wsj">{{cite news |last=McMillan |first=Robert |title=Exclusive: AI Just Found a Bug That Puts up to 70% of the World's Websites at Risk |url=https://www.wsj.com/tech/cybersecurity/ai-just-found-a-bug-that-puts-up-to-70-of-the-worlds-websites-at-risk-fd0902ea |work=The Wall Street Journal |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref>。2024 年,一名 PHP 核心开发者在安全审计中发现了其中一个漏洞背后的内存耗尽(out-of-memory)错误,但开发团队未能就修复方式达成一致,加上当时还没有已知的利用方法,问题被搁置<ref name="tnw">{{cite news |last=Constantin |first=Ana Maria |title=PHP knew about one of the flaws in 2024 but could not agree a fix |url=https://thenextweb.com/news/php-foundation-structural-failure-2024-flaw-leak |work=The Next Web |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref><ref name="phpf">{{cite web |title=Today's PHP Security Release, and How We're Strengthening PHP Security |url=https://thephp.foundation/blog/2026/10/21/todays-php-security-release-and-how-were-strengthening-php-security/ |website=The PHP Foundation |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref>。 |
|||
| ⚫ | |||
PHP 广泛用于内容管理系统和各类网站后台,也随部分主机控制面板和设备一起分发<ref name="huntress">{{cite web |last=Hammond |first=John |title=Rapid Response: php2shell, Leaked Critical PHP Vulnerabilities (CVE-2026-109618 & CVE-2026-109619) |url=https://www.huntress.com/blog/php2shell-leaked-critical-php-vulnerabilities |website=Huntress |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref>。根据 W3Techs 的统计,在能识别服务器端[[编程]]语言的网站中,约 69% 使用 PHP<ref name="w3techs">{{cite web |title=Usage statistics of PHP for websites |url=https://w3techs.com/technologies/details/pl-php |website=W3Techs |access-date=2026-11-19 |language=en}}</ref>。 |
|||
==Patches== |
|||
The maintainers of PHP released patched versions of PHP 8.2, 8.3, 8.4, and 8.5 (8.2.35, 8.3.36, 8.4.27, and 8.5.12).<ref name="oct21" /> Source code patches were released for version 7.4, 8.0, and 8.1, but no official updated binaries for those versions were released as they are considered [[Software release life cycle#End-of-life|end of life]].<ref name="oct21" /> Temporary mitigations were also published, but the maintainers said there were no complete mitigations and that updating was the only safe choice.<ref name="oct21" /> Both vulnerabilities were published through [[GitHub]] security advisories on 21 October 2026 at 13:34 UTC,<ref>{{cite web|url=https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w|title=RCE via OOM corruption|date=21 October 2026|access-date=21 October 2026}}</ref><ref>{{cite web|url=https://github.com/php/php-src/security/advisories/GHSA-6wmf-4rv5-p3rp|title=RCE via stale global state|date=21 October 2026|access-date=21 October 2026}}</ref> 26 minutes before the announced release time, with the PHP website updated shortly thereafter.<ref>{{Cite web |last=Scherzer |first=Daniel |date=22 October 2026 |title=Blog: PHP2Shell: a Timeline |url=https://scherzer.dev/Blog/20261022-php2shell-timeline |access-date=22 October 2026 |website=scherzer.dev |language=en}}</ref> |
|||
| ⚫ | |||
The PHP maintainers announced the update early and before release, after news of the vulnerabilities leaked on 20 October on the [[Hacker News]] forums,<ref>{{Cite web |title=Tell HN: 2x PHP RCE CVEs with CVSS 10.0 Incoming |url=https://news.ycombinator.com/item?id=50167754 |archive-url=https://web.archive.org/web/20261021192245/https://news.ycombinator.com/item?id=50167754 |archive-date=21 October 2026 |access-date=22 October 2026 |website=news.ycombinator.com |language=en}}</ref> in a post on [[X (social network)|X]] by cybersecurity company watchTowr labs, and in a [[proof-of-concept]] exploit video mistakenly released by Calif.<ref name="Khandelwal2026-1">{{cite news |last1=Khandelwal |first1=Swati |title=PHP2Shell: Two Unpatched Critical PHP RCE Flaws (CVSS 9.2) Trigger Emergency Security Alert |url=https://thehackernews.com/2026/10/php2shell-two-unpatched-critical-php.html |access-date=21 October 2026 |work=The Hacker News |date=21 October 2026 |language=en}}</ref>{{Unreliable source? |reason="The Hacker News" uses AI for article images, so it likely also uses AI for article text. |date=October 2026}}<ref name="McMillan2026" details="{{subref|q=News of the patch leaked out Tuesday, in a post to Hacker News, just under two days before the patch release.}}" /><ref name="Constantin2026" /> The early notice on PHP.net encouraged users to prepare and update as soon as the patch was released.<ref name="oct21" /> One security firm, Sansec, expected "mass attacks to start within 15 minutes of the release".<ref>{{Cite web |last=Goodin |first=Dan |date=20 October 2026 |title=PHP warns it plans to release 2 emergency patches imminently |url=https://arstechnica.com/security/2026/10/php-maintainers-tell-web-devs-to-prepare-themselves-for-critical-security-patches/ |access-date=21 October 2026 |website=Ars Technica |language=en|archive-url=https://web.archive.org/web/20261021121524/https://arstechnica.com/security/2026/10/php-maintainers-tell-web-devs-to-prepare-themselves-for-critical-security-patches/|archive-date=21 October 2026|url-status=live}}</ref> Proof-of-concept exploits, write-ups, and partial mitigations started circulating on the [[Internet]] before the end of the embargo, after development platform Chainguard released patched versions of the software early; this allowed attackers to determine what code had been changed.<ref name="Abrams" /><ref>{{Cite web |title=Only for the curious... |url=https://jackalsyn.com/posts/php-up-2026.html |access-date=21 October 2026 |website=jackalsyn.com}}</ref><ref name="Constantin2026" /> |
|||
两项漏洞由两方独立发现。2026 年 8 月,Calif 的研究者 Ryan Austin 在源码审计中借助 OpenAI 的 GPT-5.6 Sol 模型发现了它们,这项工作属于 OpenAI 的「Patch the Planet」项目<ref name="wsj" /><ref name="nyt1">{{cite news |last=Volz |first=Dustin |title=A Hacking Tool Built With A.I. Can Breach Phones Without a Click |url=https://www.nytimes.com/2026/09/08/us/politics/calif-ai-worm-wechat-hack.html |work=The New York Times |date=2026-09-08 |access-date=2026-11-19 |language=en}}</ref>。Wiz 的研究者使用 Gemini 4 Argon、GPT-5.6 Sol 以及自研的 Wiz Atlas 工具,独立得到了相同的结果<ref name="reuters" />。「PHP2Shell」这个名字由 Wiz 提出,意指攻击者可以借此在受影响的服务器上执行 shellcode<ref name="rf">{{cite web |title=PHP2Shell Exploitation: Two Critical PHP Flaws Explained |url=https://www.recordedfuture.com/blog/php2shell-vulnerability-exploitation |website=Recorded Future |access-date=2026-11-19 |language=en}}</ref>。 |
|||
[[Amazon Web Services|Amazon]] Threat Intelligence identified a PHP2Shell exploitation attempt dating back to 17 October 2026, in MadPot telemetry, four days before public disclosure.<ref>{{Cite web |date=21 October 2026 |title=Amazon Threat Intelligence identifies PHP2Shell exploitation prior to public disclosure in MadPot {{!}} AWS Security Blog |url=https://aws.amazon.com/blogs/security/amazon-threat-intelligence-identifies-php2shell-exploitation-prior-to-public-disclosure-in-madpot/ |access-date=22 October 2026 |website=aws.amazon.com}}</ref> [[Cloudflare]] reported signs of early exploitation prior to public [[Patch (computing)|patch]] release, and deployed temporary [[web application firewall]] (WAF) rules as an attempted stopgap mitigation against the [[Vulnerability (computer security)|vulnerability]].<ref name="Gatlan2026">{{Cite web |last=Gatlan |first=Sergiu |date=21 October 2026 |title=PHP ships emergency patches for critical PHP2Shell flaws |url=https://www.bleepingcomputer.com/news/security/php-ships-emergency-patches-for-critical-php2shell-flaws/ |access-date=21 October 2026 |website=BleepingComputer |language=en-us}}</ref><ref>{{Cite news |date=21 October 2026 |title=Hold on to your butts: Web admins braced for emergency PHP updates to plug leaked exploits |url=https://www.pcgamer.com/software/security/we-expect-mass-attacks-to-start-within-15-minutes-of-the-release-web-admins-braced-for-emergency-php-updates-to-plug-leaked-high-severity-holes/ |access-date=21 October 2026 |work=PC Gamer |language=en}}</ref><ref>{{cite web |last1=Knecht |first1=Dane |title=Dane Knecht 🦭 (@dok2001) on X |url=https://x.com/dok2001/status/2112811965735202970 |website=X (formerly Twitter) |date=21 October 2026}}</ref> Security firm watchTowr said it had observed exploitation in the wild by 21 October through its [[Honeypot (computing)|honeypot]] network,<ref>{{Cite web |date=20 October 2026 |title=PHP RCE FAQ: PHP2Shell CVE-2026-109618 & CVE-2026-109619 |url=https://watchtowr.com/intelligence/php-cve-2026-109618-faq/ |access-date=21 October 2026 |website=watchTowr |language=en}}</ref> while the [[United States|US]] [[Cybersecurity and Infrastructure Security Agency]] (CISA) said it had not observed exploitation as of the same day.<ref name="Collier2026" /> |
|||
| ⚫ | PHP 开发者依照通用漏洞评分系统(CVSS)4.0 版将漏洞评为 9.2 分,属于「严重」等级;安全公司 watchTowr 则给出了满分 10.0 的评价<ref name="announce">{{cite web |title=php.announce: [ANNOUNCE] Upcoming Critical PHP Security Release |url=https://news-web.php.net/php.announce/509 |website=PHP Mailing Lists |access-date=2026-11-19 |language=en}}</ref><ref name="abrams">{{cite web |last=Abrams |first=Lawrence |title=PHP warns admins of two critical flaws, emergency patches coming tomorrow |url=https://www.bleepingcomputer.com/news/security/php-warns-admins-of-two-critical-flaws-emergency-patches-coming-tomorrow/ |website=BleepingComputer |date=2026-10-20 |access-date=2026-11-19 |language=en}}</ref>。 |
||
| ⚫ | |||
[[File:Php2shell wiki.png|thumb|Warning posted on the [[English Wikipedia]] about community-owned tools being offline due to the PHP2Shell incident.]] |
|||
Approximately 69% of websites use PHP, including those that use [[content management system]]s such as [[Drupal]], [[Joomla]], and [[WordPress]], so the potential impacts were widespread.<ref name="Collier2026">{{cite news |last1=Collier |first1=Kevin |title=Critical vulnerabilities in commonly used web code spark rush to update systems |url=https://www.nbcnews.com/tech/security/critical-vulnerabilities-php-update-systems-rcna604751 |access-date=21 October 2026 |work=NBC News |date=21 October 2026 |language=en}}</ref><ref name="bbc">{{cite news |last1=Gerkin |first1=Tom |title=Websites taken down worldwide as critical PHP cyber-security update issued |url=https://www.bbc.com/news/articles/cmly0lg3w5x2o |access-date=21 October 2026 |work=BBC News |date=21 October 2026}}</ref> PHP is also bundled with vendor appliances, [[web hosting service|web host]] control panels such as [[cPanel]] and [[Plesk]], and some [[Windows]] applications.<ref>{{Cite web |last=Hammond |first=John |date=21 October 2026 |title=Rapid Response: php2shell, Leaked Critical PHP Vulnerabilities (CVE-2026-109618 & CVE-2026-109619) |url=https://www.huntress.com/blog/php2shell-leaked-critical-php-vulnerabilities |access-date=21 October 2026 |website=Huntress |language=en}}</ref> |
|||
| ⚫ | |||
Following advice from [[Computer emergency response team|CERT]]-EU and the British [[National Cyber Security Centre (United Kingdom)|National Cyber Security Centre]], many organizations across Europe took their websites offline as a precaution while the patches were pending, including the [[Netherlands|Dutch]] government portal Overheid.nl, the [[Denmark|Danish]] national school communication platform, all [[Finland|Finnish]] government public-facing web services, and all websites of the [[Ministry of the Interior (France)|French Interior Ministry]].<ref name="Satter2026">{{Cite news |last=Satter |first=Raphael |last2=Marchandon |first2=Leo |last3=Ghosh |first3=Kanjyik |last4=Pardesi |first4=Rajveer |date=21 October 2026 |title=Government websites go dark after AI-discovered flaw sparks security scramble |url=https://www.reuters.com/world/asia-pacific/eu-agency-warns-websites-may-need-be-taken-offline-php-prepares-patches-2026-10-21/ |access-date=21 October 2026 |work=Reuters |language=en}}</ref><ref name="bbc" /><ref>{{Cite web |last=Van Dessel |first=Josse |date=21 October 2026 |title=Major websites go offline as critical PHP vulnerability triggers security fears |url=https://www.brusselstimes.com/belgium/2371464/major-websites-go-offline-as-critical-php-vulnerability-triggers-security-fears |access-date=21 October 2026 |website=The Brussels Times |language=en}}</ref><ref>{{cite press release|url=https://www.ncsc.gov.uk/news/critical-security-issue-affecting-php|publisher=National Cyber Security Centre|date=21 October 2026|title=Critical security issue affecting PHP}}</ref> The US [[National Security Agency]] recommended that websites go offline if unable to update immediately.<ref name="Kan2026">{{cite news |last1=Kan |first1=Michael |title=This Flaw Is So Serious Websites Should Consider Going Offline, NSA Says |url=https://www.pcmag.com/news/php-flaw-is-so-serious-websites-should-consider-going-offline-nsa-says |access-date=21 October 2026 |work=PCMAG |date=21 October 2026 |language=en}}</ref><ref name="NSA">{{cite web|url=https://www.nsa.gov/Press-Room/Press-Releases-Statements/Press-Release-View/Article/4630238/nsa-advisory-php-updates/ |title=NSA Advisory: PHP Updates |author=<!-- not stated--> |publisher=[[National Security Agency|NSA]] Press Room |date=21 October 2026 |access-date=21 October 2026 |quote=Effective immediately, all organizations using PHP for their systems are advised to be prepared for an update addressing two critical vulnerabilities.}}</ref> The UK National Cyber Security Centre released a similar warning, urging organizations to be wary of [[backdoor (computing)|backdoors]].<ref>{{cite news |last1=Booth |first1=Robert |last2=Down |first2=Aisha |title=Flaw in PHP computer language leads to shutdown of websites around world |url=https://www.theguardian.com/technology/2026/oct/21/flaw-in-php-computer-language-leads-to-shutdown-of-websites-around-world |access-date=21 October 2026 |work=The Guardian |date=21 October 2026}}</ref> The Japanese National Cybersecurity Office advised PHP users to immediately update their systems.<ref name="ITmedia-21oct2026" /> |
|||
CVE-2026-109618 与内存耗尽时的状态损坏有关,CVE-2026-109619 则与跨请求残留的全局状态有关,两者都可能导致远程代码执行<ref name="ghsa618">{{cite web |title=RCE via OOM corruption |url=https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w |website=GitHub |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref><ref name="ghsa619">{{cite web |title=RCE via stale global state |url=https://github.com/php/php-src/security/advisories/GHSA-6wmf-4rv5-p3rp |website=GitHub |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref>。按 CVSS 3.1 计算,两项漏洞的评分分别为 9.8 和 8.1;按 CVSS 4.0 计算则均为 9.2<ref name="ghsa618" /><ref name="ghsa619" />。 |
|||
The [[Wikimedia Foundation]] shut down many of their supporting services, and [[Internet forum|forum]] sites [[4chan]] and [[Something Awful]] went offline.<ref name="Collier2026" /><ref name="Tauber-2026">{{Cite web |last=Tauber |first=Olivia |date=21 October 2026 |title=PHP vulnerability: Which websites and services are affected? |url=https://mashable.com/tech/php-vulnerability-websites-offline-affected-services |access-date=21 October 2026 |website=Mashable |language=en}}</ref><ref name="Kan2026" /> Parts of the Japanese internet also went offline, including games such as ''[[Umamusume: Pretty Derby]]'', ''[[Granblue Fantasy]]'', ''[[Princess Connect! Re:Dive]]'', and numerous online commerce sites.<ref name="ITmedia-21oct2026">{{cite news|url=https://www.itmedia.co.jp/news/article/2610/21/2000002472/|date=21 October 2026|title=著名ITサービス相次いで緊急メンテへ コドモン、シャドバ、BASE、さくらのレンタルサーバなど 「PHP」脆弱性に起因か|trans-title=Several prominent IT services—including Codmon, Shadowverse, BASE, and Sakura Rental Server—have initiated emergency maintenance, likely due to a vulnerability in PHP|publisher=ITmedia|access-date=21 October 2026 |language=ja}}</ref><ref name="Tauber-2026" /> The [[Internet Archive]] briefly shut down to fix the issue.<ref>{{Cite web |last=Smith |first=Paul |last2=Mizen |first2=Ronald |date=21 October 2026 |title=AI just discovered a bug putting 70pc of world's websites at risk |url=https://www.afr.com/world/north-america/websites-go-dark-as-ai-discovered-bug-sparks-global-security-scramble-20261022-p617nf |access-date=22 October 2026 |website=Australian Financial Review |language=en}}</ref> |
|||
漏洞位于 PHP 解释器本身,因此受影响的不仅是调用特定函数的应用,还包括以常见方式运行 PHP 的服务器<ref name="wiz">{{cite web |title=PHP2Shell: AI uncovers critical RCE vulnerabilities affecting 70% of the Internet |url=https://www.wiz.io/blog/php2shell-php-rce |website=Wiz Blog |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref>。除 PHP 8.2、8.3、8.4、8.5 外,7.4、8.0、8.1 等已停止支持的版本同样受这些问题影响<ref name="oct21" />。 |
|||
| ⚫ | |||
== 修补 == |
|||
Researchers at Wiz stated that the issue was on par with [[Heartbleed]], a 2014 vulnerability that affected an encryption library used by about two-thirds of the web at the time.<ref>{{cite news |last1=Eadicicco |first1=Lisa |title=Global websites shut down after AI found a critical flaw affecting 70% of the internet {{!}} CNN Business |url=https://edition.cnn.com/2026/10/21/tech/php2shell-vulnerability-ai |access-date=22 October 2026 |work=CNN |date=21 October 2026 |language=en}}</ref> Commentary in ''[[The Guardian]]'' noted that [[the PHP Foundation]], which maintains the PHP language, only had 13 full- and part-time employees, and relied on financial contributions, whereas AI research, which was credited with helping discover the vulnerability, received "billions" in investment.<ref>{{cite news |last1=Taylor |first1=Josh |title=What is PHP, and how bad is the computer language flaw causing website shutdowns globally? |url=https://www.theguardian.com/technology/2026/oct/22/what-is-php-computer-language-flaw-causing-global-website-shutdowns |access-date=22 October 2026 |work=The Guardian |date=22 October 2026}}</ref> Coverage in ''[[The New York Times]]'' said that PHP was "pervasive" and speculated that "everyday users" could have their personal [[data]] put at risk.<ref>{{Cite news |last=Adam |first=Karla |last2=Volz |first2=Dustin |date=22 October 2026 |title=What Is PHP? Why Are Government and Business Websites Going Offline? |url=https://www.nytimes.com/2026/10/22/technology/what-is-php-vulnerability-risks.html |access-date=22 October 2026 |work=The New York Times |language=en-US |issn=0362-4331}}</ref> |
|||
PHP 维护团队发布了 PHP 8.2.35、8.3.36、8.4.27 和 8.5.12,分别对应 8.2、8.3、8.4、8.5 四个分支<ref name="oct21" />。对于已经终止支持的 PHP 7.4、8.0 和 8.1,官方只提供了源代码补丁,没有发布更新后的[[二进制]]文件<ref name="oct21" />。官方同时给出了一些临时缓解措施,但表示没有一种措施能完全消除风险,升级到修补版本是唯一安全的选择<ref name="oct21" />。 |
|||
| ⚫ | |||
* [[Log4Shell]], a similarly named vulnerability |
|||
两项漏洞的安全公告于 2026 年 10 月 21 日 13 时 34 分([[协调世界时|UTC]])通过 [[GitHub]] 发布,比原定的 14 时提前了 26 分钟,PHP 官网随后更新<ref name="scherzer">{{cite web |last=Scherzer |first=Daniel |title=Blog: PHP2Shell: a Timeline |url=https://scherzer.dev/Blog/20261022-php2shell-timeline |website=scherzer.dev |date=2026-10-22 |access-date=2026-11-19 |language=en}}</ref><ref name="ghsa618" /><ref name="ghsa619" />。主机控制面板 cPanel 和 CloudLinux 在各自的[[软件]]源中提供了回移补丁<ref name="cpanel">{{cite web |title=Critical PHP Security Release - CVE-2026-109618 and CVE-2026-109619 |url=https://support.cpanel.net/hc/en-us/articles/44397389677335-Critical-PHP-Security-Release-CVE-2026-109618-and-CVE-2026-109619 |website=cPanel |date=2026-10-22 |access-date=2026-11-19 |language=en}}</ref><ref name="cloudlinux">{{cite web |last=Galov |first=Niko |title=PHP CVE-2026-109618 and CVE-2026-109619: CloudLinux Package Status and Imunify360 Protection |url=https://blog.cloudlinux.com/php-cve-2026-109618-and-cve-2026-109619/ |website=CloudLinux |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref>;志愿维护者 Ondřej Surý 提前拿到了修复代码,并为旧版本准备了可以直接安装的软件包,使[[管理员]]不必自行编译 PHP<ref name="bbcsury">{{cite web |title=The PHP developer who became the unsung hero of the internet |url=https://www.bbc.co.uk/news/articles/cw30ejqljl43o |website=BBC News |date=2026-10-24 |access-date=2026-11-19 |language=en}}</ref><ref name="atlantic">{{cite web |last=Warzel |first=Charlie |title='If Anything Happens to This Guy ... Everyone Is Screwed' |url=https://www.theatlantic.com/technology/2026/10/man-who-saved-internet-php-vulnerability/689123/ |work=The Atlantic |date=2026-10-22 |access-date=2026-11-19 |language=en}}</ref>。 |
|||
=== 提前披露 === |
|||
PHP 维护团队之所以提前公布消息,是因为漏洞信息在 10 月 20 日已经外泄,渠道包括 Hacker News 上的匿名帖、watchTowr 在 X 上的帖子,以及 Calif 误发的一段概念验证利用视频<ref name="hn">{{cite web |title=Tell HN: 2x PHP RCE CVEs with CVSS 10.0 Incoming |url=https://news.ycombinator.com/item?id=50167754 |website=Hacker News |date=2026-10-20 |access-date=2026-11-19 |language=en}}</ref><ref name="wsj" /><ref name="tnw" />。PHP.net 的提前公告呼吁使用者做好准备,在补丁发布后立即更新<ref name="oct21" />。安全公司 Sansec 当时预计,「大规模攻击会在补丁发布后 15 分钟内开始」<ref name="goodin">{{cite web |last=Goodin |first=Dan |title=PHP warns it plans to release 2 emergency patches imminently |url=https://arstechnica.com/security/2026/10/php-maintainers-tell-web-devs-to-prepare-themselves-for-critical-security-patches/ |website=Ars Technica |date=2026-10-20 |access-date=2026-11-19 |language=en}}</ref>。在保密期限结束前,网络上已经开始流传概念验证代码、技术分析和部分缓解措施,原因是开发平台 Chainguard 提前发布了修补后的版本,攻击者因此可以比对出修改了哪些代码<ref name="abrams" /><ref name="tnw" />。 |
|||
== 影响 == |
|||
[[File:Wikimedia Phabricator PHP2Shell.png|thumb|维基媒体基金会的 Phabricator 在漏洞修补前暂停服务的画面]] |
|||
PHP 在网站中的普遍使用,使这两项漏洞的潜在影响范围很广。除内容管理系统外,PHP 也随部分厂商设备、虚拟主机管理面板和 [[Windows]] 应用程序分发<ref name="huntress" />。 |
|||
根据欧盟电脑紧急应变小组(CERT-EU)和英国国家网络安全中心(NCSC)的建议,欧洲多国机构在等待补丁期间预防性地将网站下线,包括荷兰政府门户 Overheid.nl、丹麦全国学校通讯平台、芬兰政府的全部对外网络服务,以及法国内政部下属地方行政机关的网站<ref name="reuters" /><ref name="bbc">{{cite news |last=Gerkin |first=Tom |title=Websites taken down worldwide as critical PHP cyber-security update issued |url=https://www.bbc.com/news/articles/cmly0lg3w5x2o |work=BBC News |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref>。美国国家安全局建议,无法立即更新的网站应考虑暂时下线<ref name="kan" /><ref name="nsa">{{cite web |title=NSA Advisory: PHP Updates |url=https://www.nsa.gov/Press-Room/Press-Releases-Statements/Press-Release-View/Article/4630238/nsa-advisory-php-updates/ |publisher=National Security Agency |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref>;英国 NCSC 也发出类似警告,提醒各机构留意后门风险<ref name="guardian">{{cite news |last1=Booth |first1=Robert |last2=Down |first2=Aisha |title=Flaw in PHP computer language leads to shutdown of websites around world |url=https://www.theguardian.com/technology/2026/oct/21/flaw-in-php-computer-language-leads-to-shutdown-of-websites-around-world |work=The Guardian |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref>。日本国家网络安全办公室建议 PHP [[用户]]立即更新系统<ref name="itmedia" />。加拿大政府部分网站依据加拿大网络安全中心的指引临时下线<ref name="cp24">{{cite web |last=Beauchemin |first=Genevieve |title=Canadian apps and government websites go offline to ward off online danger |url=https://www.cp24.com/news/canada/2026/10/21/canadian-apps-and-government-websites-go-offline-to-ward-off-online-danger/ |website=CP24 |date=2026-10-22 |access-date=2026-11-19 |language=en}}</ref>,新加坡网络安全局也敦促当地机构尽快修补<ref name="cna">{{cite web |title=Singapore organisations urged to patch critical PHP flaws immediately amid cyberattack threat |url=https://www.channelnewsasia.com/singapore/php-vulnerabilities-csa-singapore-firms-cybersecurity-6482006 |website=CNA |date=2026-10-22 |access-date=2026-11-19 |language=en}}</ref><ref name="csasg">{{cite web |title=Critical Vulnerabilities in PHP (PHP2Shell) |url=https://www.csa.gov.sg/alerts-and-advisories/alerts/al-2026-151/ |website=Cyber Security Agency of Singapore |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref>。 |
|||
维基媒体基金会关闭了多个支持服务,论坛网站 4chan 和 Something Awful 也暂时下线<ref name="nbc" /><ref name="mashable">{{cite web |last=Tauber |first=Olivia |title=PHP vulnerability: Which websites and services are affected? |url=https://mashable.com/tech/php-vulnerability-websites-offline-affected-services |website=Mashable |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref>;互联网档案馆曾短暂停止服务以处理相关问题<ref name="afr">{{cite news |last1=Smith |first1=Paul |last2=Mizen |first2=Ronald |title=AI just discovered a bug putting 70pc of world's websites at risk |url=https://www.afr.com/world/north-america/websites-go-dark-as-ai-discovered-bug-sparks-global-security-scramble-20261022-p617nf |work=Australian Financial Review |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref>。日本多家网站和在线服务因应这次漏洞进行紧急维护,包括托育机构管理系统 CoDMON、SAKURA internet 的租用服务器、网店平台 BASE、视频分享网站 Niconico、创作社区 pixiv,以及《赛马娘 Pretty Derby》《Shadowverse: Worlds Beyond》等游戏<ref name="itmedia" /><ref name="vgc">{{cite news |last=Scullion |first=Chris |title=Capcom has temporarily delisted Street Fighter 5 and turned off its servers as it works on PHP security issue |url=https://www.videogameschronicle.com/news/capcom-has-temporarily-delisted-street-fighter-5-and-turned-off-its-servers-as-it-works-on-php-security-issue/ |work=Video Games Chronicle |date=2026-10-27 |access-date=2026-11-19 |language=en}}</ref>。 |
|||
== 漏洞利用 == |
|||
亚马逊威胁情报团队在 MadPot 遥测数据中发现,早在 2026 年 10 月 17 日,也就是公开披露前四天,就已经出现了针对 PHP2Shell 的利用尝试<ref name="aws">{{cite web |title=Amazon Threat Intelligence identifies PHP2Shell exploitation prior to public disclosure in MadPot |url=https://aws.amazon.com/blogs/security/amazon-threat-intelligence-identifies-php2shell-exploitation-prior-to-public-disclosure-in-madpot/ |website=AWS Security Blog |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref>。[[Cloudflare]] 表示在补丁发布前就观察到了早期利用迹象,并部署了临时的网页应用防火墙(WAF)规则作为过渡措施<ref name="gatlan">{{cite web |last=Gatlan |first=Sergiu |title=PHP ships emergency patches for critical PHP2Shell flaws |url=https://www.bleepingcomputer.com/news/security/php-ships-emergency-patches-for-critical-php2shell-flaws/ |website=BleepingComputer |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref>。watchTowr 称其蜜罐网络到 10 月 21 日已观察到实际环境中的利用活动,而美国网络安全和基础设施安全局(CISA)则表示截至同日尚未观察到漏洞被利用<ref name="watchtowr">{{cite web |title=PHP RCE FAQ: PHP2Shell CVE-2026-109618 & CVE-2026-109619 |url=https://watchtowr.com/intelligence/php-cve-2026-109618-faq/ |website=watchTowr |date=2026-10-20 |access-date=2026-11-19 |language=en}}</ref><ref name="nbc" />。 |
|||
10 月 25 日,安全研究员 Jaydip Modhwadia 在一项名为「Steal My Bitcoin」的在线安全挑战中,利用 PHP2Shell 在运行未修补版本 PHP 的服务器上取得了远程代码执行权限,证明该漏洞在特定条件下确实可以被利用<ref name="register">{{cite web |title=UK pentester 'killa' claims $2K Bitcoin prize in PHP2Shell capture-the-flag contest |url=https://assets.theregister.com/2026/10/26/202616/ |website=The Register |date=2026-10-26 |access-date=2026-11-19 |language=en}}</ref>。 |
|||
== 评价 == |
|||
Wiz 的研究者认为,这次事件的影响可与 2014 年的心脏出血漏洞相比:当年的漏洞影响 OpenSSL,而当时约三分之二的网站使用这一加密库<ref name="cnn">{{cite news |last=Eadicicco |first=Lisa |title=Global websites shut down after AI found a critical flaw affecting 70% of the internet |url=https://edition.cnn.com/2026/10/21/tech/php2shell-vulnerability-ai |work=CNN |date=2026-10-21 |access-date=2026-11-19 |language=en}}</ref>。《纽约时报》称 PHP 的使用「无处不在」,并推测普通用户的个人[[数据]]也可能面临风险<ref name="nyt2">{{cite news |last1=Adam |first1=Karla |last2=Volz |first2=Dustin |title=What Is PHP? Why Are Government and Business Websites Going Offline? |url=https://www.nytimes.com/2026/10/22/technology/what-is-php-vulnerability-risks.html |work=The New York Times |date=2026-10-22 |access-date=2026-11-19 |language=en}}</ref>。《卫报》的评论指出,维护 PHP 的 PHP 基金会只有 13 名全职和兼职员工,主要依靠捐款运作,而协助发现漏洞的人工智能研究获得了「数十亿」美元的投资<ref name="guardian2">{{cite news |last=Taylor |first=Josh |title=What is PHP, and how bad is the computer language flaw causing website shutdowns globally? |url=https://www.theguardian.com/technology/2026/oct/22/what-is-php-computer-language-flaw-causing-global-website-shutdowns |work=The Guardian |date=2026-10-22 |access-date=2026-11-19 |language=en}}</ref>。 |
|||
== 参考文献 == |
|||
== References == |
|||
{{Reflist}} |
{{Reflist}} |
||
== |
== 外部链接 == |
||
*[https://www.php.net/archive/2026.php#2026-10-21-5 Announcement by the PHP Project] |
|||
*[https:/ |
* [https://php2shell.com php2shell.com]([[英文]]) |
||
*[https://www. |
* [https://www.php.net/archive/2026.php#2026-10-21-5 PHP 项目安全公告](英文) |
||
* [https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w CVE-2026-109618 安全公告](英文) |
|||
{{Hacking in the 2020s}} |
|||
* [https://github.com/php/php-src/security/advisories/GHSA-6wmf-4rv5-p3rp CVE-2026-109619 安全公告](英文) |
|||
* [https://calif.io/php2shell Calif 对漏洞的说明](英文) |
|||
* [https://www.wiz.io/blog/php2shell-php-rce Wiz 对漏洞的说明](英文) |
|||
[[Category: |
[[Category:计算机安全]] |
||
[[Category: |
[[Category:软件漏洞]] |
||
[[Category:PHP]] |
[[Category:PHP]] |
||
2026年11月19日 (四) 11:09的最新版本
CaelLab 的 Phabricator 在漏洞修补前暂停服务的公告 | |
| 类型 | 计算机安全漏洞 |
|---|---|
| CVE 编号 | CVE-2026-109618、CVE-2026-109619 |
| CVSS 评分 | 9.2(CVSS 4.0,严重) |
| 发现日期 | 2026年8月 |
| 公开日期 | 2026年10月20日 |
| 修补日期 | 2026年10月21日 |
| 发现者 | Calif、OpenAI、Wiz |
| 影响软件 | PHP 5.4 至 8.5 |
| 网站 | php2shell.com |
PHP2Shell 是 2026 年公开的两项 PHP 高危漏洞的合称,编号分别为 CVE-2026-109618 和 CVE-2026-109619。两者都是 PHP 解释器中的内存安全问题,影响 PHP 5.4 至 8.5 版本,可导致远程代码执行(RCE)。PHP 是使用最广泛的服务器端编程语言之一,这两项漏洞在公开时被认为可能影响全球约七成的网站。
漏洞由美国安全公司 Calif 的研究者借助人工智能发现,以色列与美国的云安全公司 Wiz 也独立发现了同样的问题。PHP 维护团队于 2026 年 10 月 20 日提前公布消息,次日在发布紧急补丁的同时公开了漏洞细节[1][2]。由于影响范围大,多国网络安全机构建议无法立即更新的机构将网站临时下线,维基媒体基金会、互联网档案馆等网站以及日本多家网络服务在修补期间暂停了服务[3][4][5]。
PHP 5.4 于 2012 年发布,这两项漏洞从那时起便存在于 PHP 的源代码中[6]。内存安全方面的问题在更早的时候就有人指出,但当时认为实际利用并不可行,因此没有采取行动[7][8]。2024 年,一名 PHP 核心开发者在安全审计中发现了其中一个漏洞背后的内存耗尽(out-of-memory)错误,但开发团队未能就修复方式达成一致,加上当时还没有已知的利用方法,问题被搁置[9][10]。
PHP 广泛用于内容管理系统和各类网站后台,也随部分主机控制面板和设备一起分发[11]。根据 W3Techs 的统计,在能识别服务器端编程语言的网站中,约 69% 使用 PHP[12]。
两项漏洞由两方独立发现。2026 年 8 月,Calif 的研究者 Ryan Austin 在源码审计中借助 OpenAI 的 GPT-5.6 Sol 模型发现了它们,这项工作属于 OpenAI 的「Patch the Planet」项目[8][13]。Wiz 的研究者使用 Gemini 4 Argon、GPT-5.6 Sol 以及自研的 Wiz Atlas 工具,独立得到了相同的结果[4]。「PHP2Shell」这个名字由 Wiz 提出,意指攻击者可以借此在受影响的服务器上执行 shellcode[14]。
PHP 开发者依照通用漏洞评分系统(CVSS)4.0 版将漏洞评为 9.2 分,属于「严重」等级;安全公司 watchTowr 则给出了满分 10.0 的评价[15][16]。
CVE-2026-109618 与内存耗尽时的状态损坏有关,CVE-2026-109619 则与跨请求残留的全局状态有关,两者都可能导致远程代码执行[17][18]。按 CVSS 3.1 计算,两项漏洞的评分分别为 9.8 和 8.1;按 CVSS 4.0 计算则均为 9.2[17][18]。
漏洞位于 PHP 解释器本身,因此受影响的不仅是调用特定函数的应用,还包括以常见方式运行 PHP 的服务器[19]。除 PHP 8.2、8.3、8.4、8.5 外,7.4、8.0、8.1 等已停止支持的版本同样受这些问题影响[2]。
PHP 维护团队发布了 PHP 8.2.35、8.3.36、8.4.27 和 8.5.12,分别对应 8.2、8.3、8.4、8.5 四个分支[2]。对于已经终止支持的 PHP 7.4、8.0 和 8.1,官方只提供了源代码补丁,没有发布更新后的二进制文件[2]。官方同时给出了一些临时缓解措施,但表示没有一种措施能完全消除风险,升级到修补版本是唯一安全的选择[2]。
两项漏洞的安全公告于 2026 年 10 月 21 日 13 时 34 分(UTC)通过 GitHub 发布,比原定的 14 时提前了 26 分钟,PHP 官网随后更新[20][17][18]。主机控制面板 cPanel 和 CloudLinux 在各自的软件源中提供了回移补丁[21][22];志愿维护者 Ondřej Surý 提前拿到了修复代码,并为旧版本准备了可以直接安装的软件包,使管理员不必自行编译 PHP[23][24]。
PHP 维护团队之所以提前公布消息,是因为漏洞信息在 10 月 20 日已经外泄,渠道包括 Hacker News 上的匿名帖、watchTowr 在 X 上的帖子,以及 Calif 误发的一段概念验证利用视频[25][8][9]。PHP.net 的提前公告呼吁使用者做好准备,在补丁发布后立即更新[2]。安全公司 Sansec 当时预计,「大规模攻击会在补丁发布后 15 分钟内开始」[26]。在保密期限结束前,网络上已经开始流传概念验证代码、技术分析和部分缓解措施,原因是开发平台 Chainguard 提前发布了修补后的版本,攻击者因此可以比对出修改了哪些代码[16][9]。

PHP 在网站中的普遍使用,使这两项漏洞的潜在影响范围很广。除内容管理系统外,PHP 也随部分厂商设备、虚拟主机管理面板和 Windows 应用程序分发[11]。
根据欧盟电脑紧急应变小组(CERT-EU)和英国国家网络安全中心(NCSC)的建议,欧洲多国机构在等待补丁期间预防性地将网站下线,包括荷兰政府门户 Overheid.nl、丹麦全国学校通讯平台、芬兰政府的全部对外网络服务,以及法国内政部下属地方行政机关的网站[4][27]。美国国家安全局建议,无法立即更新的网站应考虑暂时下线[7][28];英国 NCSC 也发出类似警告,提醒各机构留意后门风险[29]。日本国家网络安全办公室建议 PHP 用户立即更新系统[5]。加拿大政府部分网站依据加拿大网络安全中心的指引临时下线[30],新加坡网络安全局也敦促当地机构尽快修补[31][32]。
维基媒体基金会关闭了多个支持服务,论坛网站 4chan 和 Something Awful 也暂时下线[3][33];互联网档案馆曾短暂停止服务以处理相关问题[34]。日本多家网站和在线服务因应这次漏洞进行紧急维护,包括托育机构管理系统 CoDMON、SAKURA internet 的租用服务器、网店平台 BASE、视频分享网站 Niconico、创作社区 pixiv,以及《赛马娘 Pretty Derby》《Shadowverse: Worlds Beyond》等游戏[5][35]。
亚马逊威胁情报团队在 MadPot 遥测数据中发现,早在 2026 年 10 月 17 日,也就是公开披露前四天,就已经出现了针对 PHP2Shell 的利用尝试[36]。Cloudflare 表示在补丁发布前就观察到了早期利用迹象,并部署了临时的网页应用防火墙(WAF)规则作为过渡措施[37]。watchTowr 称其蜜罐网络到 10 月 21 日已观察到实际环境中的利用活动,而美国网络安全和基础设施安全局(CISA)则表示截至同日尚未观察到漏洞被利用[38][3]。
10 月 25 日,安全研究员 Jaydip Modhwadia 在一项名为「Steal My Bitcoin」的在线安全挑战中,利用 PHP2Shell 在运行未修补版本 PHP 的服务器上取得了远程代码执行权限,证明该漏洞在特定条件下确实可以被利用[39]。
Wiz 的研究者认为,这次事件的影响可与 2014 年的心脏出血漏洞相比:当年的漏洞影响 OpenSSL,而当时约三分之二的网站使用这一加密库[40]。《纽约时报》称 PHP 的使用「无处不在」,并推测普通用户的个人数据也可能面临风险[41]。《卫报》的评论指出,维护 PHP 的 PHP 基金会只有 13 名全职和兼职员工,主要依靠捐款运作,而协助发现漏洞的人工智能研究获得了「数十亿」美元的投资[42]。
- ↑ PHP: News Archive - 20 Oct 2026. www.php.net. 2026-10-20 [2026-11-19] (English).
- ↑ 2.0 2.1 2.2 2.3 2.4 2.5 PHP: News Archive - 21 Oct 2026. www.php.net. 2026-10-21 [2026-11-19] (English).
- ↑ 3.0 3.1 3.2 Collier, Kevin. Critical vulnerabilities in commonly used web code spark rush to update systems. NBC News. 2026-10-21 [2026-11-19] (English).
- ↑ 4.0 4.1 4.2 Satter, Raphael; Marchandon, Leo; Ghosh, Kanjyik; Pardesi, Rajveer. Government websites go dark after AI-discovered flaw sparks security scramble. Reuters. 2026-10-21 [2026-11-19] (English).
- ↑ 5.0 5.1 5.2 著名ITサービス相次いで緊急メンテへ コドモン、シャドバ、BASE、さくらのレンタルサーバなど 「PHP」脆弱性に起因か. ITmedia. 2026-10-21 [2026-11-19] (日本語).
- ↑ PHP: Releases. www.php.net. [2026-11-19] (English).
- ↑ 7.0 7.1 Kan, Michael. This Flaw Is So Serious Websites Should Consider Going Offline, NSA Says. PCMag. 2026-10-21 [2026-11-19] (English).
- ↑ 8.0 8.1 8.2 McMillan, Robert. Exclusive: AI Just Found a Bug That Puts up to 70% of the World's Websites at Risk. The Wall Street Journal. 2026-10-21 [2026-11-19] (English).
- ↑ 9.0 9.1 9.2 Constantin, Ana Maria. PHP knew about one of the flaws in 2024 but could not agree a fix. The Next Web. 2026-10-21 [2026-11-19] (English).
- ↑ Today's PHP Security Release, and How We're Strengthening PHP Security. The PHP Foundation. 2026-10-21 [2026-11-19] (English).
- ↑ 11.0 11.1 Hammond, John. Rapid Response: php2shell, Leaked Critical PHP Vulnerabilities (CVE-2026-109618 & CVE-2026-109619). Huntress. 2026-10-21 [2026-11-19] (English).
- ↑ Usage statistics of PHP for websites. W3Techs. [2026-11-19] (English).
- ↑ Volz, Dustin. A Hacking Tool Built With A.I. Can Breach Phones Without a Click. The New York Times. 2026-09-08 [2026-11-19] (English).
- ↑ PHP2Shell Exploitation: Two Critical PHP Flaws Explained. Recorded Future. [2026-11-19] (English).
- ↑ php.announce: [ANNOUNCE] Upcoming Critical PHP Security Release. PHP Mailing Lists. [2026-11-19] (English).
- ↑ 16.0 16.1 Abrams, Lawrence. PHP warns admins of two critical flaws, emergency patches coming tomorrow. BleepingComputer. 2026-10-20 [2026-11-19] (English).
- ↑ 17.0 17.1 17.2 RCE via OOM corruption. GitHub. 2026-10-21 [2026-11-19] (English).
- ↑ 18.0 18.1 18.2 RCE via stale global state. GitHub. 2026-10-21 [2026-11-19] (English).
- ↑ PHP2Shell: AI uncovers critical RCE vulnerabilities affecting 70% of the Internet. Wiz Blog. 2026-10-21 [2026-11-19] (English).
- ↑ Scherzer, Daniel. Blog: PHP2Shell: a Timeline. scherzer.dev. 2026-10-22 [2026-11-19] (English).
- ↑ Critical PHP Security Release - CVE-2026-109618 and CVE-2026-109619. cPanel. 2026-10-22 [2026-11-19] (English).
- ↑ Galov, Niko. PHP CVE-2026-109618 and CVE-2026-109619: CloudLinux Package Status and Imunify360 Protection. CloudLinux. 2026-10-21 [2026-11-19] (English).
- ↑ The PHP developer who became the unsung hero of the internet. BBC News. 2026-10-24 [2026-11-19] (English).
- ↑ Warzel, Charlie. 'If Anything Happens to This Guy ... Everyone Is Screwed'. The Atlantic. 2026-10-22 [2026-11-19] (English).
- ↑ Tell HN: 2x PHP RCE CVEs with CVSS 10.0 Incoming. Hacker News. 2026-10-20 [2026-11-19] (English).
- ↑ Goodin, Dan. PHP warns it plans to release 2 emergency patches imminently. Ars Technica. 2026-10-20 [2026-11-19] (English).
- ↑ Gerkin, Tom. Websites taken down worldwide as critical PHP cyber-security update issued. BBC News. 2026-10-21 [2026-11-19] (English).
- ↑ NSA Advisory: PHP Updates. National Security Agency. 2026-10-21 [2026-11-19] (English).
- ↑ Booth, Robert; Down, Aisha. Flaw in PHP computer language leads to shutdown of websites around world. The Guardian. 2026-10-21 [2026-11-19] (English).
- ↑ Beauchemin, Genevieve. Canadian apps and government websites go offline to ward off online danger. CP24. 2026-10-22 [2026-11-19] (English).
- ↑ Singapore organisations urged to patch critical PHP flaws immediately amid cyberattack threat. CNA. 2026-10-22 [2026-11-19] (English).
- ↑ Critical Vulnerabilities in PHP (PHP2Shell). Cyber Security Agency of Singapore. 2026-10-21 [2026-11-19] (English).
- ↑ Tauber, Olivia. PHP vulnerability: Which websites and services are affected?. Mashable. 2026-10-21 [2026-11-19] (English).
- ↑ Smith, Paul; Mizen, Ronald. AI just discovered a bug putting 70pc of world's websites at risk. Australian Financial Review. 2026-10-21 [2026-11-19] (English).
- ↑ Scullion, Chris. Capcom has temporarily delisted Street Fighter 5 and turned off its servers as it works on PHP security issue. Video Games Chronicle. 2026-10-27 [2026-11-19] (English).
- ↑ Amazon Threat Intelligence identifies PHP2Shell exploitation prior to public disclosure in MadPot. AWS Security Blog. 2026-10-21 [2026-11-19] (English).
- ↑ Gatlan, Sergiu. PHP ships emergency patches for critical PHP2Shell flaws. BleepingComputer. 2026-10-21 [2026-11-19] (English).
- ↑ PHP RCE FAQ: PHP2Shell CVE-2026-109618 & CVE-2026-109619. watchTowr. 2026-10-20 [2026-11-19] (English).
- ↑ UK pentester 'killa' claims $2K Bitcoin prize in PHP2Shell capture-the-flag contest. The Register. 2026-10-26 [2026-11-19] (English).
- ↑ Eadicicco, Lisa. Global websites shut down after AI found a critical flaw affecting 70% of the internet. CNN. 2026-10-21 [2026-11-19] (English).
- ↑ Adam, Karla; Volz, Dustin. What Is PHP? Why Are Government and Business Websites Going Offline?. The New York Times. 2026-10-22 [2026-11-19] (English).
- ↑ Taylor, Josh. What is PHP, and how bad is the computer language flaw causing website shutdowns globally?. The Guardian. 2026-10-22 [2026-11-19] (English).
- php2shell.com(英文)
- PHP 项目安全公告(英文)
- CVE-2026-109618 安全公告(英文)
- CVE-2026-109619 安全公告(英文)
- Calif 对漏洞的说明(英文)
- Wiz 对漏洞的说明(英文)