Updating our coordinated vulnerability disclosure policy timelines
打开互动全文版(逐段中英对照 + 针对本篇提问)→本文宣布对协调漏洞披露(CVD)政策作出调整,以应对前沿 AI 模型在发现漏洞方面能力大幅提升的趋势。对于高危和严重问题,披露窗口从 90 天缩短至 30 天;其他问题则缩短至 45 天。新规适用于 2027 年 1 月 1 日及之后报告的漏洞,而正在进行中的报告仍沿用原有截止期限。若维护者未作回应,升级至外部协调者的时限从 30 天缩短至 15 天;补丁发布后,完整技术细节的共享时间从 45 天缩短至 30 天。核心论点是:传统披露规范假设修复以人类速度推进,且独立重新发现漏洞的可能性较低,但如今这两个假设都不再成立,因为 AI 可以协助开发修复方案,且漏洞被重新发现的情况正在增多。作者总结认为,90 天窗口已无法让漏洞在足够长的时间内保持私密,因此缩短时间线更能匹配 AI 的发展进度并兼顾防御方的需求;同时,对于难以修复的缺陷、正在被积极利用的漏洞以及未经审查的 AI 发现结果,仍保留例外,相关支持项目也旨在减轻维护者负担。
This article announces changes to a coordinated vulnerability disclosure (CVD) policy in response to frontier AI models becoming far more capable at discovering vulnerabilities. The disclosure window is shortened from 90 days to 30 days for high- and critical-severity issues and to 45 days for all other issues, applying to vulnerabilities reported on or after January 1, 2027, while in-progress reports keep existing deadlines. Escalation to an external coordinator now occurs after 15 days instead of 30 if a maintainer does not respond, and full technical details are shared 30 days instead of 45 after a patch is available. The core argument is that traditional disclosure norms assumed fixes moved at human speed and that independent rediscovery was unlikely, but neither assumption holds today because AI can help develop fixes and vulnerability rediscovery is rising. The author concludes that a 90-day window no longer keeps vulnerabilities private long enough, so shorter timelines better match AI progress and balance defenders' needs, while exceptions remain for hard-to-fix flaws, active exploitation, and unreviewed AI findings, and support programs aim to reduce maintainer burden.
* 01 应对 AI 驱动的漏洞发现
* 01 Responding to AI-enabled vulnerability discovery
过去几个月里,前沿模型在发现漏洞方面的能力大幅提升。我们仍然乐观地认为,这将帮助防御方比以往任何时候都更快地发现并修复漏洞。然而,AI 的进步速度已经改变了我们对自身披露实践的思考方式。
Over the last several months, frontier models have become much better at discovering vulnerabilities. We remain optimistic that this will help defenders find and fix vulnerabilities faster than ever before. However, the speed at which AI is improving has changed how we think about our own disclosure practices.
我们正在缩短协调漏洞披露(CVD)政策中的披露窗口:对于高严重性和严重性问题,从 90 天缩短至 30 天;对于所有其他问题,缩短至 45 天。新的时间线适用于 2027 年 1 月 1 日及之后向供应商和维护者报告的漏洞。截至该日期仍在进行中的报告将保留其现有截止期限。
We're shortening the disclosure window in our coordinated vulnerability disclosure (CVD) policy from 90 days to 30 days for high- and critical-severity issues, and to 45 days for all other issues. The new timelines apply to vulnerabilities reported to vendors and maintainers on or after January 1, 2027. In-progress reports as of that date will keep their existing deadlines.
除了缩短披露窗口外,我们还将做出两项相关调整。第一,如果维护者未对我们的初始漏洞报告作出回应,我们将在 15 天后(而非 30 天后)升级至外部漏洞协调员。第二,在补丁可用后,我们将在 30 天后(而非 45 天后)分享完整技术细节。政策的其余部分保持不变。
In addition to shortening the disclosure window, we are making two related changes. First, we will aim to escalate to an external vulnerability coordinator after 15 days instead of 30 if a maintainer does not respond to our initial vulnerability report. Second, we will wait 30 days instead of 45 after a patch is available before sharing full technical details. The rest of our policy remains the same.
最后,有一些高严重性和严重性漏洞是我们 90 多天前报告的,如今已超出我们现行 CVD 政策中的截止期限,但尚未公开披露。我们现在正通知这些项目的维护者,将为他们额外提供 30 天时间;此后,我们将按照自 2027 年 1 月 1 日起生效的更新政策,在我们的仪表板上发布这些报告。
Finally, there are high- and critical-severity vulnerabilities that we reported over 90 days ago and that now exceed the deadline in our current CVD policy that have not yet been disclosed publicly. We are now notifying the maintainers of these projects that we are providing them an additional 30 days, after which time we will publish these reports on our dashboard in line with our updated policy starting January 1, 2027.
许多协同披露规范,包括我们自身政策中的规范,都是在 AI 能够发现漏洞之前很久就已制定的。这些政策假设修复以人类的速度推进,并且同一个缺陷不太可能被独立地再次发现。如今这两个假设都不再成立。模型现在可以帮助开发修复方案,而一个模型能够发现的缺陷,越来越可能被另一个模型发现。随着这些能力的提升,我们正看到漏洞被重复发现的比率上升。当漏洞可以预期在数月内保持私密时,90 天的窗口是合理的。我们不再认为它能够保持私密,而这些变更旨在跟上 AI 能力的进展,并为防御方取得恰当的平衡。
Many coordinated disclosure norms, including those found in our own policy, were developed well before AI could discover vulnerabilities. These policies assumed that fixes moved at human speed and that independent rediscovery of the same bug was unlikely. Neither assumption holds today. Models can now help develop fixes, and a bug that one model can find is increasingly likely to be found by another. We are seeing a higher rate of vulnerability rediscovery as these capabilities increase. A 90-day window made sense when a vulnerability could be expected to stay private for months. We no longer believe it can, and these changes are intended to keep pace with progress in AI capabilities and strike the right balance for defenders.
有些漏洞仍然无法被快速修复。难以部署的软件(例如关键基础设施)中的缺陷,以及需要修改规范或 RFC 的缺陷,并不总能在 30 天或 45 天内解决。在这些情况下,我们将与供应商共同商定修复时间表。对于任何正被积极利用的漏洞,我们七天的披露窗口保持不变。这一新的政策更新将不适用于尚未经过人工审查的 AI 发现的漏洞,例如由 OSS Scanner 发现的漏洞。
Some vulnerabilities still can't be fixed quickly. Flaws in hard-to-deploy software, such as critical infrastructure, and flaws that require changes to a specification or RFC can't always be resolved in 30 or 45 days. In these cases, we will work with the vendor on a remediation timeline. Our seven-day disclosure window for any vulnerability under active exploitation remains unchanged. This new policy update will not apply to AI-discovered findings that have not received human review, such as those found by OSS Scanner.
我们认识到,更短的时间线可能会给软件维护者带来更大压力。为减轻这一负担,我们将继续在每份报告中附上可操作的指导,并在可能的情况下附上补丁或缓解措施,以最大程度地帮助维护者确认发现并修复漏洞。在向单个项目发送大量发现之前,我们也将继续与维护者商定可持续的节奏。
We recognize that shorter timelines may put more pressure on software maintainers. To reduce that burden, we will continue to include actionable guidance with each report, along with a patch or mitigation where possible, to best enable the maintainer to confirm a finding and fix the vulnerability. We will also continue to agree on a sustainable pace with maintainers before sending a large volume of findings to a single project.
我们提供多项计划,帮助维护者和防御方适应这一新的节奏。关键开源项目的维护者可以申请 OSS Scanner,这是一项免费服务,会定期用我们最强的模型扫描其代码,并直接将发现发送给他们。符合条件的维护者和贡献者可以申请 Claude for Open Source Program,免费获得六个月的 Claude Ultra。安全专业人员(包括开源维护者)可以申请我们的 Cyber Verification Program,该计划会调整 Claude 的防护措施,以支持合法的防御性工作。
We offer programs to help maintainers and defenders work at this new pace. Maintainers of critical open-source projects can apply to OSS Scanner, a no-cost service that periodically scans their code with our strongest models and sends them findings directly. Eligible maintainers and contributors can apply to the Claude for Open Source Program for six months of Claude Ultra at no cost. And security professionals, including open-source maintainers, can apply to our Cyber Verification Program, which tailors Claude's safeguards to enable legitimate defensive work.