Edition of Saturday 14 November 2026

Policy and Disclosure: 2026 Edition

Comments on “Policy and Disclosure: 2026 Edition”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Google Project Zero is replacing its "90 + 30" disclosure policy with "Full X," under which details go public X days after a report, with no separate patch soak time. The deadline is 90 days now, 60 from February 2, 2027, and 30 from January 3, 2028. Grace periods and variant rules are gone; exceptions cover exploited, already-public and vendor-requested cases. Project Zero cites LLM-assisted attacks and its own higher report volume, without supporting data. Vendors should prepare for faster fixes and non-patch mitigations.

Read the original at projectzero.google. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 6 of 123 with a score of 0.74. The panel rated it highest on new information (0.93) and reader interest (0.87), lowest on technical depth (0.42). The judges disagreed most on substantiated (spread 0.41), so the story is marked contested.

AI judgeJudge 2claude-haiku-5-5
Major vulnerability disclosure policy change from Google Project Zero, driven by AI-accelerated exploitation; highly relevant to security and builders, though it is policy rather than technical depth.
AI judgeJudge 3gpt-5.6-luna
A primary-source policy change from 90+30 disclosure to staged Full 90/60/30 deadlines directly affects vulnerability remediation, patch gaps, and security operations. It offers rationale and exceptions, though limited empirical evidence and technical implementation detail.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.74total under rubric v2.3Contestedjudges differ by 0.41 on substantiated

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.76
  • Reader interest0.87
  • Audience breadth0.81
  • Practical relevance0.73
  • Substantiated0.51
  • Technical depth0.42
  • New information0.93
  • Counts against: Promotional0.05
  • Counts against: Overclaim0.16

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.730.700.830.760.13+0.24+0.181
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.810.900.900.870.09+0.26+0.226
Audience breadthHow many people who build technology does it concern?0.840.800.780.810.06+0.13+0.105
Practical relevanceHow useful is it to someone who builds software or tech products?0.620.700.860.730.24+0.22+0.160
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.310.500.720.510.41 , above the contested threshold+0.05+0.026
Technical depthHow technically substantive is it?0.580.200.480.420.38+0.05+0.021
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.900.900.980.930.08+0.05+0.046
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.080.050.030.050.05−0.19−0.010
OverclaimDo the headline or conclusions claim more than the body supports?0.210.200.080.160.13−0.11−0.018
Sum of contributions+0.737
Claim-check penalty0.000
Total, as published0.737

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #6 on Rubric, 14 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-14/6/"><img src="https://rubric.hrih.si/badge/2026-11-14/6.svg" alt="Ranked #6 on Rubric, 14 Nov 2026" width="238" height="28"></a>

Claim check

Claim check: 2 matches source · 6 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. No source givenDate

    Since 2021, Project Zero has followed a "90 + 30" disclosure policy giving vendors up to 90 days to fix a vulnerability plus 30 days of soak time for patch rollout.

    The article gives no link or citation for it.

    The article says

    “Since 2021, Project Zero has followed a “90 + 30” vulnerability disclosure policy, allowing vendors up to 90 days to remediate a vulnerability plus an extra 30 days “soak time”…”

    The source says

    No source to compare with.

  2. No source givenNumber

    Project Zero is now finding several vulnerabilities a week in targets where it once found a few a year.

    The article gives no link or citation for it.

    The article says

    “We are finding several vulnerabilities a week in targets where we once found a few vulnerabilities a year”

    The source says

    No source to compare with.

  3. No source givenCausal conclusion

    LLMs have reduced attackers' time to reverse engineer and exploit a vulnerability from a patch so that zero patch-to-exploitation time is a reasonable model of attacker behavior.

    The article gives no link or citation for it.

    The article says

    “LLMs have also decreased the time it takes for attackers to reverse engineer and exploit a vulnerability based on a patch, to the extent that zero patch-to-exploitation time is a…”

    The source says

    No source to compare with.

  4. No source givenCausal conclusion

    AI-assisted vulnerability discovery and exploitation has made the previous remediation timeline in Project Zero's policy insufficient.

    The article gives no link or citation for it.

    The article says

    “The advent of AI-assisted vulnerability discovery and exploitation has changed the threat landscape such that the vulnerability remediation timeline encouraged by our disclosure policy is clearly insufficient”

    The source says

    No source to compare with.

  5. No source givenVersion

    Project Zero's new policy is "Full 90" starting immediately, disclosing vulnerabilities 90 days after they are reported to the vendor.

    The article gives no link or citation for it.

    The article says

    “Starting today, our policy is “Full 90”, i.e. vulnerabilities will be disclosed 90 days after they are reported to the vendor”

    The source says

    No source to compare with.

  6. No source givenDate

    Project Zero will move to a "Full 60" policy on February 2, 2027 and a "Full 30" policy on January 3, 2028.

    The article gives no link or citation for it.

    The article says

    “On February 2, 2027, we will move to a “Full 60” policy where vulnerabilities are disclosed after 60 days”

    The source says

    No source to compare with.

  7. Matches sourceVersion

    Actively exploited in-the-wild vulnerabilities will be handled under Google's application security vulnerability disclosure policy.

    The cited source says the same thing.

    The article says

    “ITW vulnerabilities will be handled according to Google’s application security vulnerability disclosure policy”

    The source says

    “When we observe a previously unknown and unpatched vulnerability in software under active exploitation (a “0day”), we believe that more urgent action—within 7 days—is appropriate”

    Source cited by the article: about.google/company-info/appsecurity

  8. Matches sourceNumber

    Project Zero has granted exceptions to its policy, including for Spectre and Meltdown.

    The cited source says the same thing.

    The article says

    “Project Zero has occasionally granted exceptions to our policy on rare occasions, including Spectre and Meltdown”

    The source says

    “Yes, in 10 out of 2219 cases the disclosure deadlines for Project Zero’s issues were extended by Google”

    Source cited by the article: projectzero.google/vulnerability-disclosure-faq.html

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 8 pts, front page

Discussion on Hacker News

Recorded for context only, checked 15 Nov 2026, 20:44 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Policy and Disclosure: 2026 Edition”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.