← Voltar ao feed
low

Google Project Zero replaces '90+30' with 'Full X' disclosure policy: Full 90 now, Full 60 from Feb 2027, Full 30 from Jan 2028

6 fonte(s) · 6 atualização(ões) · publicado 15/11/2026 23:07 · coletado há 19 horas

Matéria consolidada. Reúne 7 matérias que o Tifon tinha publicado separadamente sobre a mesma história. A IA reescreveu o relatório com o que as 6 fontes trouxeram em 17/11/2026 00:04; os links antigos trazem para cá.

Fontes: darkreading.com ↗ bleepingcomputer.com ↗ securityweek.com ↗ infosecurity-magazine.com ↗ helpnetsecurity.com ↗ securityonline.info ↗

Google Project Zero announced a new disclosure policy, Full X, in a post dated November 13 (infosecurity-magazine.com). Engineer Natalie Silvanovich announced the change (securityweek.com). It replaces the "90 + 30" rule in use since 2021. Technical details are now published X days after the vendor is notified, whether or not a fix has shipped (securityweek.com, bleepingcomputer.com). X starts at 90 days for new bugs (securityonline.info), falls to 60 days on February 2, 2027, and reaches 30 days on January 3, 2028 (helpnetsecurity.com, infosecurity-magazine.com, securityweek.com, bleepingcomputer.com). The 30-day extension was removed on November 13 (bleepingcomputer.com). Project Zero ties the change to LLM-assisted vulnerability discovery and exploitation. It says patch-to-exploit time is now close to zero and that it finds several bugs a week in targets where it once found a few a year (helpnetsecurity.com, infosecurity-magazine.com). Dark Reading frames the change as a cut from 120 days to 30 over 14 months and says it has split security experts (darkreading.com). This is a policy change, not a vulnerability or an incident, and no CVEs or exploitation are reported.

Detalhes técnicos

  • The 30-day patch-adoption "soak" period, the grace period and the variant policy are removed (infosecurity-magazine.com, helpnetsecurity.com). Project Zero says soak time no longer makes sense because patches can be reverse engineered almost immediately (securityonline.info, infosecurity-magazine.com). Bleepingcomputer.com adds that AI makes it easier for attackers to reverse-engineer patches as soon as they ship and to build working exploits.
  • Neither bug severity nor fix status moves the disclosure date. Project Zero will still track fix status and share user safety guidance (securityonline.info, helpnetsecurity.com).
  • Exceptions: bugs exploited in the wild, which get a 7-day window (securityweek.com); bugs whose details are already public or leaked; and cases where the vendor asks Project Zero to publish (securityonline.info, infosecurity-magazine.com, securityweek.com, bleepingcomputer.com). Actively exploited bugs fall under Google's application security disclosure policy, and hardware bugs may still get extra time, as Spectre and Meltdown did (helpnetsecurity.com). Securityweek.com says most other special cases are removed.
  • Additional rationale: LLMs raise the chance of bug collisions during an embargo (helpnetsecurity.com).
  • Vendors consulted warned that unfixed bugs could reach attackers. They also warned of distorted prioritisation, with Project Zero reports placed above more severe issues, and of vendors giving up on deadlines they cannot meet (helpnetsecurity.com, infosecurity-magazine.com, bleepingcomputer.com). Silvanovich says the phased schedule is meant to push vendors to improve remediation and responds to these concerns (securityweek.com). The gradual phase-in is why the move is not straight to 30 days (bleepingcomputer.com).
  • The policy assumes Project Zero reports are high quality. Vendors may reasonably treat low-quality reports differently (securityweek.com).

Remediação

  • Vendors of software that Project Zero tests should plan for 90-, then 60-, then 30-day deadlines. They should shorten patch development and release workflows (securityonline.info, helpnetsecurity.com, securityweek.com) and speed up triage, fixing and patch delivery (bleepingcomputer.com).
  • Vendors should prepare non-patch mitigations, such as disabling code paths. They should also plan a response for a serious bug being disclosed before it is fixed (helpnetsecurity.com).
  • Qualys' Ivan Milenkovic said monthly patching is now slower than disclosure and that patch programmes were not built for this arrival rate (infosecurity-magazine.com). Defenders should shorten patch cycles, apply patches faster because post-patch exploit development is getting quicker (bleepingcomputer.com), and expect details of unfixed bugs to become public sooner (securityweek.com).

Relatos divergentes

  • Special rules: securityonline.info says there are no special rules and that only exploitation, leaks or vendor requests allow earlier release. helpnetsecurity.com says hardware bugs may still get extra time and that exploited bugs follow Google's application security policy. securityweek.com says exploited bugs get a 7-day window and that serious flaws may still get exceptions, as with Spectre and Meltdown. bleepingcomputer.com says Google may withhold disclosure at its discretion, as with Spectre and Meltdown. The sources do not settle this, and none cites Project Zero's own post. The securityweek.com and bleepingcomputer.com reports are the most recent.
  • Baseline deadline: darkreading.com describes the cut as 120 days to 30 days over 14 months, counting the old 90+30 total. The other sources describe a current 90-day deadline with the 30-day grace period removed. Darkreading.com had only a short teaser available, so its schedule and expert reactions are unconfirmed.

Linha do tempo

  1. darkreading.com ↗ · pub. 16/11/2026 19:08 · coletado 16/11 21:00 só resumo do feed

    Google Project Zero to cut vulnerability disclosure deadline for vendors from 120 days to 30 over 14 months, dividing experts

    ler a análise desta fonte

    Google Project Zero, one of the oldest running bug disclosure programs, announced it will shorten its public disclosure timeline for vendors from 120 days to 30 days, phased in over the next 14 months. According to Dark Reading, the change has split security experts. The article text available for this record is only a short teaser, and no web research was performed, so the exact phase-in schedule, the rationale and the reactions of named experts are not confirmed here. This is policy news with no direct threat, vulnerability or exploitation attached.

  2. bleepingcomputer.com ↗ · pub. 16/11/2026 18:31 · coletado 16/11 19:00

    Google Project Zero shortens vulnerability disclosure deadline to 30 days by 2028, citing AI-accelerated exploitation

    ler a análise desta fonte

    Google Project Zero is replacing its "90+30" disclosure policy with shorter, fixed deadlines. It cites AI-accelerated vulnerability discovery and exploitation. The change is gradual. It began on November 13, when the 30-day extension was removed. The deadline drops to 60 days on February 2, 2027, and to 30 days on January 3, 2028. Once the deadline expires, details are published even if no fix is available. Exceptions allow earlier disclosure when a flaw is exploited in the wild, when others have already published details, or when the vendor requests it. They also allow non-disclosure at Google's discretion, as with Spectre and Meltdown.

    Technical Details

    Project Zero says AI makes it easier for attackers to reverse-engineer patches as soon as they ship and to build working exploits. Vendors warned that moving straight to 30 days could expose users to unfixed flaws and distort patch prioritization toward Project Zero findings. This is why the move is gradual.

    Remediation

    Vendors should speed up triage, fixing and patch delivery. Defenders should plan to apply patches faster, because exploit development after a patch is getting quicker. The article is the only source used. No research on Google's own channels was carried out.

  3. securityweek.com ↗ · pub. 16/11/2026 12:31 · coletado 16/11 13:00

    Google Project Zero adopts 'Full X' disclosure policy, dropping the 30-day grace period and shrinking deadlines to 30 days by 2028

    ler a análise desta fonte

    Google Project Zero announced a new 'Full X' disclosure policy, citing AI-assisted vulnerability discovery and exploitation. Since November 13, Project Zero publishes vulnerability details 90 days after reporting them to the vendor, whether or not a fix has shipped. The earlier 30-day patch-adoption grace period no longer applies. The window drops to 60 days on February 2, 2027, and to 30 days on January 3, 2028. Engineer Natalie Silvanovich announced the change.

    Technical Details

    • Most 'special cases' are removed. Exceptions remain for bugs exploited in the wild (7-day window) and flaws already made public by others.
    • A vendor can request early publication. Serious flaws may still get exceptions, as with Spectre and Meltdown.
    • Silvanovich says the phased schedule is meant to push vendors to improve remediation. It also responds to concerns about users being exposed to unpatched bugs, vendors rushing fixes at the expense of more severe earlier reports, and vendors that cannot meet the new deadlines.
    • The policy assumes Project Zero reports are high quality. Vendors may reasonably treat low-quality reports differently.

    Remediation

    Vendors whose products Project Zero researches should shorten their patch cycles to meet the 90-day, then 60-day, then 30-day deadlines. Defenders should expect details of unpatched bugs to become public sooner. No vendor advisory or primary source was consulted beyond the article.

  4. infosecurity-magazine.com ↗ · pub. 16/11/2026 09:15 · coletado 16/11 10:02

    Google Project Zero replaces "90+30" with "Full X" disclosure policy, cutting deadline to 60 days in 2027 and 30 days in 2028

    ler a análise desta fonte

    Google Project Zero has dropped its "90 + 30" disclosure policy and adopted a new policy called Full X. Under it, technical details are published X days after the vendor is notified, whether or not a fix exists. The policy starts at Full 90, moves to Full 60 on February 2, 2027 and reaches Full 30 on January 3, 2028. Project Zero announced the change in a November 13 post and tied it to AI-assisted vulnerability discovery and exploitation. It said it now finds several vulnerabilities a week in targets where it once found a few a year. This is a policy change, not an attack, and no vulnerability or exploitation is reported. The article is the only source used; no research was done on Project Zero's own post.

    Technical Details

    • The 30-day "soak time", the grace period and the variant policy are removed.
    • Three exceptions remain: vulnerabilities exploited in the wild, bugs whose details are already public, and cases where the vendor asks Project Zero to publish.
    • Project Zero said soak time no longer makes sense because attackers can quickly work out bug details from a patch.
    • Vendors consulted warned that an immediate change could expose unfixed bugs, push them to prioritise Project Zero reports over more severe ones, or lead some to stop trying.
    • Project Zero will still track fix status, but fix status will no longer decide when details are published.

    Remediation

    • Qualys' Ivan Milenkovic said monthly patching is now slower than disclosure and that patch programmes were not built for this arrival rate (infosecurity-magazine.com).
    • Defenders should shorten patch cycles and prepare for details of unfixed bugs to become public.
  5. helpnetsecurity.com ↗ · pub. 16/11/2026 03:30 · coletado 16/11 04:02

    Google Project Zero adopts "Full X" policy: details published 90 days after report, falling to 60 (Feb 2027) and 30 days (Jan 2028)

    ler a análise desta fonte

    Google Project Zero will publish technical details of the vulnerabilities it reports 90 days after reporting them to the vendor, whether or not a fix has shipped. The deadline drops to 60 days on February 2, 2027 and to 30 days on January 3, 2028. The policy is called "Full X" and replaces the "90 + 30" rule used since 2021, so the 30-day patch-adoption (soak) period is removed. Project Zero says it made the change because large language models (LLMs) speed up bug discovery and the conversion of patches into exploits, and because its volume of findings has risen. This is a policy announcement, not a vulnerability or an incident. The article names no CVEs, and the research did not include a check of Project Zero's own channels.

    Technical Details

    • Reasons given: LLMs help attackers find and exploit bugs faster, and raise the chance of bug collisions during an embargo. Patch-to-exploit time is now treated as close to zero. Project Zero is finding several bugs a week in targets where it once found a few a year.
    • Exceptions: actively exploited bugs fall under Google's application security disclosure policy. Project Zero may publish at its discretion if others have already published details. A vendor may ask Project Zero to publish a bug it reported. Hardware bugs may still get extra time, as Spectre and Meltdown did.
    • Neither severity nor whether a bug is fixed will move the disclosure date. Project Zero will still track and communicate fix status.
    • Vendors raised concerns about unfixed bugs reaching attackers, about prioritisation distortion, and about vendors giving up on deadlines they cannot meet.

    Remediation

    Vendors of software that Project Zero tests should plan for the shorter deadlines. They should speed up patch rollout and prepare non-patch mitigations, such as disabling code paths. They should also plan a response for the case where a serious bug is disclosed before it is fixed.

  6. securityonline.info ↗ · pub. 15/11/2026 23:07 · coletado 16/11 00:00 primeiro registro

    Google Project Zero adopts 'Full X' disclosure policy, phasing from Full 90 to Full 30 by 2028 due to AI-speed exploitation

    ler a análise desta fonte

    Google Project Zero announced a new disclosure policy called Full X. It replaces the earlier "90 plus 30" timeline. Under it, a bug becomes public X days after the vendor is notified, whether or not a fix is ready. Project Zero justifies the change by saying LLMs let attackers find and exploit bugs faster. It also says patches can be reverse engineered almost immediately, so a patch soak period no longer has value. This is a policy change, not a vulnerability or an incident. The article cites only the Project Zero post. No independent research was run for this record.

    Technical Details

    • Disclosure happens X days after vendor notice, with no grace period and no special rules. Only active exploitation, public leaks or vendor requests allow earlier release.
    • Bug severity no longer delays the public date.
    • Rollout: Full 90 applies immediately to new bugs. Full 60 starts on 2 February 2027. Full 30 starts on 3 January 2028.
    • Project Zero will still track fix status and share user safety guidance. Fix status will not change the release date.

    Remediation

    Vendors should shorten their patch development and release workflows. They should be ready to ship fixes within 90 days now, then 60 days, then 30 days.