OpenAI 披露 Patch the Planet 计划借助 GPT-5.6 Sol 发现 PHP 关键漏洞并协调全球修复

来源:OpenAI:官网动态(RSS · 排除企业/客户案例) 2026年10月21日 15:00 AIHOT 评分:74 精选
摘要:OpenAI 宣布在过去两个月牵头维护者、研究者与安全厂商联盟,修复 PHP 的关键漏洞,其中 Calif 用 GPT-5.6 Sol 发现一处严重缺陷,Wiz 也独立发现并报告了这两个漏洞,PHP 维护者主导修复和发布。
推荐理由:OpenAI 亲述 PHP 漏洞的 AI 发现与全球协同修复过程,并给出五阶段披露框架,读者可了解 AI 时代漏洞响应的运作方式。
# OpenAI 披露 Patch the Planet 计划借助 GPT-5.6 Sol 发现 PHP 关键漏洞并协调全球修复 > 原标题:Patch the Planet: global response coordination as agents uncover critical vulnerabilities - 来源:OpenAI:官网动态 - 发布时间:2026-10-21T07:00:00.000Z - AIHOT:https://aihot.news/items/r4saw5foxj8v0eb82f3b66cs0 - 原文:https://openai.com/index/coordinated-disclosure-of-critical-vulnerabilities/ ## 摘要 OpenAI 宣布在过去两个月牵头维护者、研究者与安全厂商联盟,修复 PHP 的关键漏洞,其中 Calif 用 GPT-5.6 Sol 发现一处严重缺陷,Wiz 也独立发现并报告了这两个漏洞,PHP 维护者主导修复和发布。 ## 推荐理由 OpenAI 亲述 PHP 漏洞的 AI 发现与全球协同修复过程,并给出五阶段披露框架,读者可了解 AI 时代漏洞响应的运作方式。 ## 正文 · 中文译文 ## 修补地球计划:当智能体发现关键漏洞时进行全球响应协调 分享 过去两个月里,我们牵头组建了一个由维护者、研究人员和安全提供商组成的联盟,以解决 PHP 中的关键漏洞——PHP 是一种用于运行网站和 Web 应用的开源编程语言。Calif 在我們的 [Patch the Planet⁠(在新窗口中打开)](https://patchtheplanet.org/) 计划中,使用 GPT‑5.6 Sol 发现了一个关键缺陷,Wiz 也独立发现并报告了这两个漏洞。PHP 的维护者主导了修复和发布工作,我们的团队以及 Wiz、Cloudflare 等合作伙伴贡献了研究、技术支持和协调工作,以便在披露之前准备好防护措施。 对于使用 PHP 的组织来说,现在的首要任务是应用修复。我们分享了一个 PHP 版本检查器,并将推出配套的 Codex 技能,帮助运维人员识别可能易受攻击的 PHP 版本,并结合 PHP 及其提供商的指导,确定应应用哪些更新。 鉴于这些缺陷的严重性以及 PHP 的广泛使用,我们认为这是近期记忆中影响最严重的安全问题之一。它凸显了 AI 如何能够发现具有互联网规模影响的安全缺陷,但同样的能力也可以帮助攻击者快速开发攻击工具和漏洞利用程序。 据我们所知,前沿 AI 在攻击者之前发现了这些漏洞,为维护者和安全提供商打开了一个 [Defender’s Window](https://openai.com/index/the-defenders-window/),以便在披露之前准备修复和防护措施。 为了帮助更多防御者使用这些能力,我们承诺通过 [Daybreak for Frontline Defenders](https://openai.com/index/daybreak-for-frontline-defenders/) 提供 10 亿美元的补贴 [Daybreak 访问权限](https://openai.com/form/enterprise-trusted-access-for-cyber/),重点关注那些安全资源有限、负责保护关键服务的组织。 尽管这些漏洞影响重大,但它们只是我们已经发现并正在努力修复的若干重要漏洞中的一部分,我们预计未来几个月类似的发现会急剧增加。基于我们迄今为止的经验,我们分享一种适用于 AI 时代的拟议方法,用于应对广泛使用软件中的关键漏洞,并请求安全社区帮助改进这一框架。它汇集了我们的模型、安全专业知识和维护者,帮助将发现转化为防护,并构建一个能够随着 AI 能力进步而扩展的响应机制。 ## 协调全球响应 让修复措施投入使用可能意味着要针对旧版本进行调整、准备提供商缓解措施,并在许多组织中更新系统。随着更多漏洞被发现,可重复的流程有助于这些团队快速行动。 通过 Patch the Planet,我们贡献了安全专业知识和模型访问权限来支持 PHP 响应,并与维护者和研究合作伙伴合作测试修复措施并准备指导。我们还帮助协调基础设施提供商为受影响系统提供防护,并联系政府网络机构,帮助指导信息传达给关键组织。这支持了由维护者主导的响应,并帮助其他防御者做好准备。 对于某些发现,研究人员可以直接与软件维护者合作调查问题并开发修复方案。其他发现则需要更广泛的响应,因为它们影响许多产品,或者因为分销商和服务提供商需要时间(如果前沿能力与广泛可用的能力差距不大,时间可能很紧张)来准备更新和防护措施。在这些情况下,所提出的框架可以帮助维护者确定需要哪些人参与并协调工作。响应可以包括五个阶段: - **验证并修复上游漏洞。**维护者、研究人员和关键的技术合作伙伴确认该发现,评估其影响,并开发与测试修复方案。这一过程包括使用前沿模型进行对抗性测试,以寻找绕过补丁的方法以及该漏洞的相关变体。 - **给受影响组织留出采取行动的时间。**我们提出一个框架,用于考虑哪些组织需要预先获得信息以准备防护措施,同时由维护者决定让谁参与。我们协助开展外联、信息共享协议以及团队之间的协调。分销商可能为较旧版本调整修复方案,托管服务提供商可能测试缓解措施,安全提供商可能准备检测或预防措施,包括 Web 应用防火墙(WAF)规则。 - **与政府合作伙伴协调,帮助保护关键系统。**政府机构在协调更广泛的响应以及帮助安全指南传达至负责关键基础设施和其他基本服务的组织方面发挥着重要作用。在 PHP 的案例中,我们与合作伙伴协作,与美国政府的多个部门接触,包括白宫的超级智能部队、国家网络主任办公室(ONCD)、网络安全和基础设施安全局(CISA),以及国际合作伙伴,以支持这项工作。 - **在受影响产品中准备更新。**随着修复方案、指南和披露计划趋于稳定,维护者可以让更多分销商、托管和服务提供商、响应团队及运营人员参与进来,准备更新并弥补覆盖缺口。 - **补丁可用后,发布指南并支持部署。**公开指南帮助人们评估自身暴露风险、找到权威更新或临时缓解措施,并检查修复是否正在运行。随着运营人员部署更新并报告需要帮助的地方,响应工作继续进行。 该框架考虑组织的防护角色,包括保护自身系统和客户、采取行动所需的时间,以及处理敏感信息的能力。同样的标准将适用于类似组织,由维护者决定在披露前让谁参与。 每位参与者都会获得开展防护工作所需的信息,从带有入侵指标的网络日志到更敏感的工作概念验证漏洞利用。即使有限的细节也可能暴露漏洞,因此我们权衡共享这些信息的风险与其所能带来的防护。 遵循该框架的团队将与维护者合作,为防御者留出准备时间,并在出现野外活跃利用、泄露、暴露性公开补丁或修复停滞导致用户风险增加时重新评估时间线。 [Patch the Planet 网站⁠(在新窗口打开)](https://patchtheplanet.org/)汇集了公开披露信息和指导,帮助运营者识别受影响的系统、找到正确的更新,并验证更新后的软件正常运行。针对 PHP,该网站提供了维护者的官方补丁和升级说明,以及我们合作伙伴的技术研究。指导内容还涵盖临时缓解措施、何时需要引入供应商或专家,以及备份与恢复。临时防护措施可以降低风险,但我们会明确说明其局限性和运维权衡。 运营者可以使用 [CISA 关于优先级排序和修复的指导⁠(在新窗口打开)](https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk),根据暴露程度、利用情况和潜在影响来评估行动速度。这可能意味着紧急打补丁、立即缓解或计划性更新,并在有需要时进行取证排查,以评估系统是否已被入侵。随着情况变化,应重新评估优先级,并制定清晰的持久修复路径。 ## 为维护者提供响应所需的能力和资源 全球协调依赖于维护软件的人们。许多项目由小型团队运营,他们在日常开发之余还要审查安全报告。这些团队需要帮助,以区分新问题与重复问题、评估影响,并在受支持的版本上测试修复。我们通过资金、能力强大的模型使用权限和实地工程支持来支持这项工作。 强大的 AI 能力正在整个行业不断进步,我们预计 AI 将在帮助防御者发现漏洞、监控系统和响应威胁方面发挥越来越大的作用。我们正在投资模型、工具和合作伙伴关系,帮助防御者将这些能力投入使用。 我们的投资包括通过 [Codex for OSS](https://openai.com/form/codex-for-oss/) 为所有维护者提供订阅,以及直接赞助 [Rust 基金会⁠(在新窗口打开)](https://rustfoundation.org/media/rust-foundation-welcomes-openai-as-platinum-member-announces-donation-to-rust-project/)等项目,用于维护者和技术工作。每个项目自行设定优先级。可复用的测试和安全工作流可以减少处理未来发现的问题所需的工作量。开源项目可以[申请 Patch the Planet⁠(在新窗口打开)](https://trailofbits.com/patch-the-planet/#apply)以获得实地支持。 我们还在为 Daybreak 校准额外的拦截分类器,以帮助降低被滥用的可能性。这涉及艰难的权衡:旨在防止滥用的防护措施也可能阻碍合法的安全工作。广泛使用能力强大的模型和有效防止滥用都至关重要。我们的目标是保留防御者发现和修复漏洞所需的能力,同时限制有害使用。随着能力进步以及我们从这些工具的使用方式中学习,我们将继续完善这一平衡。 ## 构建更安全的软件基础 随着模型能力越来越强,机会不仅限于发现和修复单个漏洞。我们希望帮助工程师从一开始就构建更安全的软件。对广泛使用的组件进行改进,可以防止缺陷或限制其影响波及许多产品和服务。 AI 可以帮助工程师理解现有代码、准备变更和开发测试,同时由维护者和安全专家验证这些变更是否保留了用户所依赖的行为。我们在几个领域看到了机会: - **从一开始就保障代码安全。** 编码模型可以帮助开发者选择更安全的默认设置、正确使用安全库,并在编写代码时捕捉风险模式。在开发过程中预防漏洞,意味着维护者和用户所需的紧急修复更少。 - **内存安全软件。** 将关键组件迁移到内存安全语言,可以消除常见类别的内存错误。AI 可以协助迁移,并通过测试和专家审查来检查行为与兼容性。 - **形式化验证。** 数学证明可以表明关键组件在既定假设下满足指定的安全属性。将这些方法应用于广泛使用的组件,有助于在依赖它们的服务和关键基础设施中排除各类漏洞。 - **更强的隔离。** 系统需要防护尚未被发现或修复的漏洞。在严格受限的沙箱中运行处理不受信任文件、图像或媒体的软件,可以在其被攻破时限制损害。AI 可以帮助工程师测试并强化广泛使用的沙箱技术,改善众多应用中的防护。 ## 帮助我们改进这一方法 我们分享这一方法,是为了让维护者、研究人员、响应团队、提供商和运营者帮助使其切实可行。我们希望了解它在哪些方面有帮助、在哪些方面可能增加延迟或负担,以及我们遗漏了什么。以往披露的案例将特别有用。 我们尤其关注: - **披露窗口。** 维护者、运营者和防御者需要多少时间来准备和部署可靠的修复?什么证据应触发更早披露,尤其是当部分用户能比其他用户更早受到保护时? - **紧急修补。** 政府或其他运营者在失去管理访问权限后,何时(如果有的话)应利用漏洞来修补其拥有或获授权管理的系统?应适用哪些保障措施?我们可以设想一种最终状态:互联网范围内始终开启对已知漏洞的扫描,并在检测到漏洞时通知站点所有者或修补系统。 - **提前通知。** 谁需要提前警告才能采取有用的保护行动,包括我们可能遗漏的防御者?分阶段通知何时比一次性通知更广泛群体效果更好,我们应如何权衡覆盖范围与泄露风险? - \*\*默认安全的软件包。\*\* 我们如何在上游修复待定期间帮助识别并修复下游软件包中的漏洞,或将修复向后移植到不再接收安全更新的旧版本?什么样的测试和维护能使这些软件包在无法及时升级时成为可靠选择? 我们也欢迎推荐能够审查该方法、质疑其假设并找出差距的独立安全专家。您的意见将帮助我们完善响应并确定支持优先级。[在此分享您的反馈⁠(在新窗口中打开)](https://docs.google.com/forms/d/e/1FAIpQLSfcynrrWRWdj0PLAwtwVg2pfr0IvyAx5HfRBYf5tZin1AMLiQ/viewform)。 - [2026](https://openai.com/news/?tags=2026) - [Daybreak](https://openai.com/news/?tags=daybreak) ## 作者 OpenAI ## 正文 · 原文 ## Patch the Planet: global response coordination as agents uncover critical vulnerabilities Share Over the past two months, we led a coalition of maintainers, researchers, and security providers to address critical vulnerabilities in PHP, an open-source programming language used to run websites and web applications. Calif identified a critical flaw using GPT‑5.6 Sol as part of our [Patch the Planet⁠(opens in a new window)](https://patchtheplanet.org/) initiative, with Wiz also independently discovering and reporting both vulnerabilities. PHP’s maintainers led the fixes and release, with our teams and partners like Wiz, Cloudflare, and others contributing research, technical support, and coordination to prepare protections ahead of disclosure. For organizations using PHP, the priority now is applying the fixes. We’re sharing a PHP version checker and we will be launching an accompanying Codex skill to help operators identify potentially vulnerable PHP versions and, alongside PHP’s and their providers’ guidance, determine which updates apply. Given the severity of these flaws and PHP’s widespread use, we consider this one of the most impactful security issues in recent memory. It highlights how AI can uncover security flaws with internet-scale impact, but the same capabilities can also help attackers rapidly develop offensive tools and exploits. To our knowledge, frontier AI found these vulnerabilities before attackers did, opening a [Defender’s Window](https://openai.com/index/the-defenders-window/) for maintainers and security providers to prepare fixes and protections ahead of disclosure. To help more defenders use these capabilities, we’ve committed $1 billion in subsidized [Daybreak access](https://openai.com/form/enterprise-trusted-access-for-cyber/) through [Daybreak for Frontline Defenders](https://openai.com/index/daybreak-for-frontline-defenders/), focused on organizations with limited security resources protecting essential services. As significant as they are, these bugs are among several significant vulnerabilities we’ve already found and are working to fix, and we expect similar findings to increase sharply in the coming months. Drawing on our experience thus far, we’re sharing a proposed approach, appropriate for the AI era, to responding to critical vulnerabilities in widely used software, and we’re asking the security community to help improve this framework. It brings together our models, security expertise, and maintainers to help turn findings into protection and build a response that can scale as AI capabilities advance. ## Coordinating a global response Getting a fix into use can mean adapting it for older releases, preparing provider mitigations, and updating systems across many organizations. A repeatable process helps those teams act quickly as more vulnerabilities are discovered. Through Patch the Planet, we contributed security expertise and model access to support the PHP response, and worked with maintainers and research partners to test fixes and prepare guidance. We also helped coordinate with infrastructure providers on protections for affected systems and engaged government cyber agencies to help guidance reach critical organizations. This supported the maintainer-led response and helped other defenders prepare. For some findings, researchers can work directly with the software’s maintainers to investigate the issue and develop a fix. Others need a wider response because they affect many products or because distributors and service providers need time (which may be in short supply if frontier capabilities are not too far ahead of those that are broadly available) to prepare updates and protections. In those cases, the proposed framework can help maintainers identify who needs to be involved and coordinate the work. The response can involve five stages: - **Validate and fix the upstream vulnerability.** The maintainer, researchers, and essential technical partners confirm the finding, assess its impact, and develop and test a fix. This process includes adversarial testing with frontier models to look for ways around the patch and related variants of the vulnerability. - **Give affected organizations time to act.** We propose a framework for considering which organizations need advance information to prepare protections, while maintainers decide whom to involve. We help with outreach, information-sharing agreements, and coordination between teams. A distributor might adapt a fix for an older release, a hosting provider might test a mitigation, and a security provider might prepare detection or prevention measures, including web application firewall (WAF) rules. - **Coordinate with government partners to help protect critical systems.** Government agencies play an essential role in coordinating a wider response and helping security guidance reach organizations responsible for critical infrastructure and other essential services. In the case of PHP, we worked, in collaboration with our partners, to engage with multiple parts of the U.S. government, including the White House’s Super Intelligence Force, the Office of the National Cyber Director (ONCD), the Cybersecurity and Infrastructure Security Agency (CISA), as well as international partners to support that effort. - **Prepare updates across affected products.** As the fix, guidance, and disclosure plans become stable, maintainers can involve additional distributors, hosting and service providers, response teams, and operators to prepare updates and address gaps in coverage. - **Once a patch is available, publish guidance and support deployment.** Public guidance helps people assess their exposure, find authoritative updates or interim mitigations, and check that a fix is running. The response continues as operators deploy updates and report where they need help. The proposed framework considers an organization’s protective role, including protecting its own systems and customers, the time needed to act, and its ability to handle sensitive information. The same criteria would apply to comparable organizations, with maintainers deciding whom to involve ahead of disclosure. Each participant receives the information needed to carry out their protective work, from network logs with indicators of compromise to more sensitive working proof-of-concept exploits. Even limited details can reveal a vulnerability, so we weigh the risk of sharing them against the protection they enable. Teams following this framework would work with maintainers to give defenders time to prepare and reassess the timeline if there’s active exploitation in the wild, a leak, a revealing public patch, or increased risk to users from stalled remediation. The [Patch the Planet website⁠(opens in a new window)](https://patchtheplanet.org/) brings together public disclosures and guidance to help operators identify affected systems, find the right update, and verify that the updated software is running properly. For PHP, it points to the maintainers’ official patch and upgrade instructions and our partners’ technical research. The guidance also covers interim mitigations, when to involve a provider or expert, and backup and recovery. Interim protections can reduce risk, but we’ll make their limits and operational tradeoffs clear. Operators can use [CISA’s guidance on prioritization and remediation⁠(opens in a new window)](https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk) to assess how quickly to act based on exposure, exploitation, and potential impact. That may mean emergency patching, immediate mitigation, or a planned update, alongside forensic triage where warranted to assess whether systems have already been compromised. Priorities should be reassessed as conditions change, with a clear path to lasting remediation. ## Giving maintainers the capacity and resources to respond Global coordination depends on the people who maintain the software. Many projects are run by small teams that review security reports alongside routine development. Those teams need help separating new issues from duplicates, assessing impact, and testing fixes across supported releases. We support that work with funding, access to capable models, and hands-on engineering help. Powerful AI capabilities are advancing across the industry, and we expect AI to play a growing role in helping defenders find vulnerabilities, monitor systems, and respond to threats. We’re investing in models, tools, and partnerships to help defenders put those capabilities to work. Our investments include subscriptions for all maintainers through [Codex for OSS](https://openai.com/form/codex-for-oss/) and direct sponsorship of projects such as the [Rust Foundation⁠(opens in a new window)](https://rustfoundation.org/media/rust-foundation-welcomes-openai-as-platinum-member-announces-donation-to-rust-project/) for maintainers and technical work. Each project sets its own priorities. Reusable tests and security workflows can reduce the effort needed to handle future findings. Open-source projects can [apply to Patch the Planet⁠(opens in a new window)](https://trailofbits.com/patch-the-planet/#apply) for hands-on support. We’re also calibrating additional blocking classifiers for Daybreak to help reduce the potential for misuse. This involves difficult tradeoffs: safeguards intended to prevent abuse can also block legitimate security work. Broad access to capable models and effective protections against misuse are both critical. Our aim is to preserve the capabilities defenders need to find and fix vulnerabilities while limiting harmful use. We’ll continue refining that balance as capabilities advance and we learn from how these tools are used. ## Building more secure software foundations As models become more capable, the opportunity extends beyond finding and fixing individual vulnerabilities. We want to help engineers build more secure software from the start. Improvements to a widely used component can prevent bugs or limit their impact across many products and services. AI can help engineers understand existing code, prepare changes, and develop tests, while maintainers and security experts verify that those changes preserve the behavior users depend on. We see opportunities in several areas: - **Secure code from the start.** Coding models can help developers choose safer defaults, use security libraries correctly, and catch risky patterns as they write. Preventing vulnerabilities during development means fewer emergency fixes for maintainers and users. - **Memory-safe software.** Moving critical components to memory-safe languages can eliminate common classes of memory errors. AI can help with migrations, with tests and expert review to check behavior and compatibility. - **Formal verification.** Mathematical proofs can show that critical components satisfy specified security properties under stated assumptions. Applying these methods to widely used components could help rule out classes of vulnerabilities across the services and critical infrastructure that depend on them. - **Stronger isolation.** Systems need protection against vulnerabilities that have not yet been found or fixed. Running software that processes untrusted files, images, or media in tightly restricted sandboxes can limit the damage if it is compromised. AI can help engineers test and strengthen widely used sandboxing technologies, improving protections across many applications. ## Help us improve this approach We’re sharing our approach so maintainers, researchers, response teams, providers, and operators can help make it workable. We want to understand where it would help, where it could add delay or burden, and what we’ve missed. Examples from past disclosures would be especially useful. We’re particularly interested in: - **Disclosure windows.** How much time do maintainers, operators, and defenders need to prepare and deploy reliable fixes? What evidence should trigger earlier disclosure, especially when some users can be protected sooner than others? - **Emergency patching.** When, if ever, should governments or other operators use a vulnerability to patch systems they own or are authorized to manage after losing administrative access? What safeguards should apply? We can imagine an end-state of internet-wide always-on scanning for known vulnerabilities, and either notifying site owners when one is detected or patching the system. - **Early notice.** Who needs advance warning to take a useful protective action, including defenders we might miss? When do staged notifications work better than notifying a wider group at once, and how should we weigh coverage against leak risk? - \*\*Secure-by-default software packages.\*\*How can we help identify and fix vulnerabilities in downstream packages while upstream fixes are pending, or backport fixes to older versions that no longer receive security updates? What testing and maintenance would make these packages reliable options when a timely upgrade isn’t feasible? We also welcome recommendations for independent security experts who can review the approach, challenge its assumptions, and identify gaps. Your input will help us refine the response and prioritize support. [Share your feedback here⁠(opens in a new window)](https://docs.google.com/forms/d/e/1FAIpQLSfcynrrWRWdj0PLAwtwVg2pfr0IvyAx5HfRBYf5tZin1AMLiQ/viewform). - [2026](https://openai.com/news/?tags=2026) - [Daybreak](https://openai.com/news/?tags=daybreak) ## Author OpenAI