How the policy changes
Project Zero announced its Full X policy on 13 November 2026. The team says it will disclose vulnerabilities 90 days after reporting them to a vendor. The deadline is planned to move to 60 days on 2 February 2027 and 30 days on 3 January 2028.
The old policy gave an additional patch adoption period in some cases. The new timeline makes the vendor response window clearer. It does not mean every vendor or researcher uses the same policy.
Prepare the fix path before a report arrives
Name the people who can assess a report, approve a code change and release an update. Keep a current inventory of products, dependencies and support contacts. Make it possible to build and test a security fix without waiting for a routine release cycle.
Set a channel for researcher communication. Acknowledge reports, ask for details that help reproduce the issue and protect sensitive evidence. Do not delay triage while teams debate whether the report is valid.
Measure time to protect users
Track the time from report to validation, patch, release and user adoption. A fix is not complete when code merges if customers cannot install it or the update does not reach supported versions.
Publish clear update instructions and monitor rollout. A web application penetration test can find weaknesses in your application, while a secure development process helps your team respond when new flaws are reported.
