📊 Full opportunity report: The 90-Day Window Closed. Nobody Sent a Notice. on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
The traditional 90-day window for responsible vulnerability disclosure has closed without any notices from vendors or researchers. This shift, driven by AI capabilities, enables attackers to develop exploits faster than ever, impacting cybersecurity practices.
The 90-day window for responsible vulnerability disclosure has officially closed without any notices from vendors or security researchers, marking a significant shift in cybersecurity dynamics. This development, confirmed by multiple security experts, underscores how AI-driven vulnerability discovery now enables exploits to be developed and weaponized faster than traditional disclosure protocols can accommodate.
Historically, the 90-day coordinated disclosure framework, popularized by Google Project Zero in 2014, provided a structured period for vendors to patch vulnerabilities after receiving reports from researchers. During this window, defenders could deploy patches before attackers could exploit the vulnerabilities publicly. However, in 2026, this model has been fundamentally compromised. Theori’s recent disclosure of the Linux kernel bug ‘Copy Fail’ exemplifies this shift: the patch was committed on April 1, 2026, and publicly disclosed on April 29, but AI systems monitoring kernel commits can now reconstruct and exploit such vulnerabilities within minutes of the commit, rendering the 28-day window dangerously obsolete.
Security experts attribute this change to advances like Theori’s Xint Code, which can rapidly analyze commit diffs and surface exploitable bugs. AI-driven tools can now produce working exploits from patches in a fraction of the time previously required, giving attackers a significant head start. This has been evidenced by recent breaches at Vercel and Canvas, where vulnerabilities at trust boundaries—such as OAuth scopes and SaaS integrations—were exploited, rather than traditional memory-safety bugs. These incidents highlight that the most critical vulnerabilities now lie at system integration points, where existing defenses like ASLR and stack canaries are less effective.
The 90-day window closed.
Nobody sent a notice.
The commit-monitoring window. The knowledge floor. And what Vercel and Canvas reveal about where the bugs actually live.
Copy Fail’s mainline patch landed April 1. Public disclosure was April 29. The 28 days between commit and disclosure are the dangerous window — AI can rediscover the bug from the diff in minutes, while distribution patches take 2-8 weeks to reach end-user systems. Three asymmetries compound: time, expertise, knowledge category. Defender disadvantage compounds across all three.
The patch is now the disclosure event.
Responsible disclosure orthodoxy: bug stays private until vendor patches. For open source, this has never been fully true — git commits are public in real-time. Copy Fail’s mainline patch landed April 1. Public disclosure was April 29. The 28 days between are the dangerous window.
fafe0fa2995a reverting the 2017 in-place AEAD optimization. Patch is now public.INSTANT
TREES
PUBLIC
AVAILABLE
SLOWLY
cybersecurity vulnerability scanning tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
“Please find a security vulnerability.”
No training required.
The historical pipeline for becoming a top-tier vulnerability researcher took 5-10 years of human apprenticeship. Kernel internals. Processor architecture. Exploit-mitigation-bypass craft. Decompiler-output reading. All baked into frontier model training data.
- CS degree with security specialization
- 3-5 years red team / CTF / firm experience
- 2-3 years senior research with reportable findings
- Tacit knowledge: kernel internals, decompiler output reading, exploit-mitigation-bypass craft
- Global pool: ~200-500 senior researchers per decade
- Apprenticeship: mentored by existing experts
- Frontier model API access ($20-200/month for individuals)
- One prompt: “Please find a security vulnerability”
- No security training required (Anthropic / AISI / CETaS verified)
- Tacit knowledge baked in from model training
- Pool of capable actors: millions globally
- Bottleneck: willingness to use it, not skill
The prompt Anthropic used to discover vulnerabilities with Mythos “essentially amounted to ‘Please find a security vulnerability in this program.'” Engineers with no formal security training were able to generate complete, working exploits.
AI-powered vulnerability detection software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Memory safety isn’t where the breaches happen anymore.
Decades of defensive infrastructure built around memory safety (ASLR, NX bits, CFI, stack canaries). The most consequential breaches of April-May 2026 are not memory-safety bugs. They are trust-boundary failures at integration seams.
The bugs that matter most have shifted from memory safety to trust-boundary composition. OAuth scopes. SaaS-to-SaaS authentication. Multi-tier account models. Third-party app permissions. Environment variable handling. Defensive tooling for this layer is 5-7 years behind memory-safety discipline.
Defensive infrastructure for memory safety is 25+ years mature. Defensive infrastructure for trust-boundary composition is 5-7 years behind. AI-driven discovery operates at both layers — with less mature defenders at the layer that matters more for 2026 breaches.
software patch management tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
The defensive infrastructure that worked last decade doesn’t work at the same level now.
Adaptation is necessary. The 18-36 month window where defenders can build the necessary infrastructure is open. Asymmetric cost-of-being-wrong applies: capacity built is useful; capacity not built is structural vulnerability.
+ SECURITY TEAMS
PUBLISHERS
POLICYMAKERS
EVERYONE ELSE
The 90-day window collapsed. The knowledge floor collapsed. The bugs moved layers. Three asymmetries compound. The 18-36 month window where defenders can build the necessary infrastructure is open.
network security monitoring devices
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Implications for Cybersecurity Defense Strategies
This development signifies a paradigm shift in cybersecurity: the traditional window for defenders to respond before exploits emerge no longer exists. Attackers leveraging AI can now identify, develop, and deploy exploits in real-time, challenging existing patching and defense models. The collapse of the knowledge floor means even non-expert actors can generate effective exploits, broadening the threat landscape. Consequently, organizations must reconsider their security approaches, focusing more on real-time monitoring, behavioral analysis, and zero-trust architectures, as the old reliance on delayed patching becomes increasingly ineffective.
Evolving Vulnerability Discovery and Disclosure Frameworks
The responsible disclosure model, established in the early 2000s, relied on the assumption that reverse engineering patches took meaningful time, giving defenders a head start. The 90-day window was designed to balance researcher incentives with vendor needs, ensuring vulnerabilities were patched before widespread exploitation. However, recent technological advancements—particularly AI-driven code analysis—have disrupted this balance. The April 2026 disclosures of the Linux kernel bug and subsequent breaches at Vercel and Canvas exemplify how AI accelerates vulnerability discovery and exploit development, rendering the traditional window ineffective and shifting the focus toward more immediate, proactive security measures.
“Our recent breach revealed vulnerabilities at the trust boundary, which are now the primary targets for attackers exploiting AI-driven discovery.”
— Vercel security spokesperson
Unclear Impact on Future Vulnerability Management
It remains unclear how organizations will adapt their vulnerability management strategies in response to the collapse of the 90-day window. The long-term effectiveness of real-time detection, AI-based monitoring, and zero-trust approaches is still being evaluated, and the pace of technological change may introduce new vulnerabilities or defense mechanisms in the coming months.
Next Steps for Cybersecurity Stakeholders
Security organizations and vendors are expected to accelerate deployment of real-time monitoring tools, AI-based threat detection, and zero-trust architectures. Regulatory bodies may also revisit disclosure requirements and breach reporting timelines. Researchers and defenders will need to develop new frameworks for rapid response, as traditional patching cycles become insufficient to counter AI-enabled exploits. Monitoring developments at major breaches like Vercel and Canvas will be crucial for understanding evolving threat patterns.
Key Questions
Why has the 90-day disclosure window become ineffective?
Because AI-driven tools can analyze patches and develop exploits within minutes, eliminating the traditional time advantage for defenders.
What types of vulnerabilities are now most targeted?
Vulnerabilities at trust boundaries, such as OAuth scopes, SaaS integrations, and environment-variable handling, are now the primary targets, rather than memory-safety bugs.
How should organizations respond to this shift?
Organizations should adopt real-time monitoring, behavioral analysis, and zero-trust security models to mitigate the faster threat landscape.
Will this change affect responsible disclosure practices?
Yes, the traditional 90-day window is no longer effective, prompting a need for new, more immediate disclosure and response protocols.
Source: ThorstenMeyerAI.com