Skip to content
TECHNOLOGY. BUSINESS. CONTEXT.Entivel company ↗
EntivelInsights

Australia · United States · Bangladesh
Original reporting & analysis

Subscribe

Google to automatically disclose qualifying bug reports

From 1 December, Google will automatically publish some Google & Alphabet Vulnerability Reward Program reports after a defined post-fix interval. The rule applies only to qualifying reports and includes privacy options.

Published Updated 2 min read
Editorial illustration of a vulnerability report moving through a software fix, waiting period and publication. Headline: Google Adds Auto-Disclosure.
Editorial illustration: Google’s policy adds automatic publication for a defined set of vulnerability reward reports after a fix and waiting period.

News | 22 November 2026

Google will automatically publish some higher-value security reports submitted to its Google & Alphabet Vulnerability Reward Program (VRP), under a disclosure policy announced on 19 November. The change starts with qualifying reports submitted on or after 1 December; it does not set a 30-day deadline for vendors to patch vulnerabilities.

Under the new rule, a report must earn at least US$10,000 from Google’s VRP. Google says publication will occur only after at least 30 days have passed since the report was fixed and at least seven days since the reward was issued and the researcher notified. Reports linked to special events or grants that may involve unreleased products and features are excluded.

That timing is a minimum period after a fix, not a guarantee that all users or downstream software makers have installed an update. Google’s announcement describes automatic disclosure of eligible reports; it does not say that every vulnerability report will be made public or that unresolved issues will be disclosed immediately.

Google says researchers can opt for anonymous disclosure and propose edits before a report is published. The company says those options are intended to address researchers’ concerns about linking their names to award amounts and to help remove identifiers, cookies and other potentially sensitive details. The announcement does not describe these options as a general right to prevent publication of a qualifying report.

The company framed the policy as a way to create a public record that can help security researchers and AI agents learn from valid reports. Google also said its VRP has seen 15 times as many duplicate reports as in 2023 and that average report text has grown threefold, which it attributes in part to AI-assisted discovery and writing. Those figures are Google’s account of activity in its program, not an industry-wide measurement.

For software maintainers and organisations that depend on upstream components, the practical distinction is between a report being fixed and the fix reaching every product in use. A public report may improve shared understanding, while the post-fix waiting period does not replace an organisation’s own software inventory, vendor-update process or assessment of whether a released fix applies to its systems. Google says the first qualifying reports are expected to begin appearing in early 2027.

From Entivel

Entivel’s Cyber Security Engineering service describes work in secure architecture, application assurance, identity and access, and remediation planning. This service information is separate from Google’s programme and policy.

Sources: Google, “Expanding Transparency: Google & Alphabet VRP Disclosure Policy Update,” 19 November 2026; Entivel Cyber Security Engineering.

THE ENTIVEL NEWSLETTER

Stay informed. See what comes next.

Technology, business and digital resilience across Australia, the United States and Bangladesh.

FROM ENTIVEL

Connect your people, finance and operations.

Explore Entivel's enterprise software and specialist engineering services.