📊 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 vulnerability disclosure has closed without any vendor notices. AI advancements now enable attackers to develop exploits faster than ever, shifting the security landscape.
The 90-day window for responsible vulnerability disclosure has officially closed without any notices from affected vendors, marking a significant shift in cybersecurity dynamics. This development is confirmed by security researchers and industry sources who note that AI tools now enable attackers to develop exploits within days of patch releases, eroding the traditional defender advantage. The change has broad implications for cybersecurity practices and incident response strategies.
Historically, the 90-day coordinated disclosure window, established around 2014 by Google Project Zero, provided vendors with a fixed period to patch vulnerabilities before public disclosure. During this window, defenders could deploy patches and mitigate risks before attackers weaponized the flaws. However, recent developments show that this window is no longer a defensive advantage. In April 2026, the Linux kernel patch for the Copy Fail vulnerability was publicly committed on April 1, with public disclosure occurring on April 29. During the four-week period, AI-powered tools enabled attackers and researchers alike to analyze the patch and develop exploits rapidly, often within hours or minutes.
Sources confirm that AI systems like Theori’s Xint Code can monitor kernel commits, identify security fixes, and reconstruct exploits in record time—far faster than traditional reverse engineering. This rapid turnaround means attackers can weaponize vulnerabilities well before patches are deployed across distributions, effectively collapsing the window defenders relied upon. Additionally, recent high-profile breaches at Vercel and Canvas highlight that the most critical vulnerabilities are now trust-bound failures at integration points—OAuth scopes, SaaS-to-SaaS authentication, environment-variable handling—not memory safety bugs at the kernel level.
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 scanner
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 exploit detection tools
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 software
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.
security incident response toolkit
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Implications of the Disappearance of the 90-Day Window
This shift signifies that the fundamental assumptions underpinning responsible disclosure are no longer valid. With AI-enabled rapid exploit development, the traditional advantage of defenders—time to patch before attacks—has evaporated. Attackers can now discover and weaponize vulnerabilities almost immediately after patches are released, increasing the risk of widespread exploitation. This change demands a reevaluation of cybersecurity strategies, emphasizing proactive defenses, continuous monitoring, and a focus on trust boundary security at the application layer.
Evolving Cybersecurity Landscape and Recent Breaches
The 90-day disclosure framework was established to balance the interests of security researchers and vendors, fostering responsible patching and disclosure practices. Since its inception, it relied on the assumption that reverse engineering patches takes significant time, and that attacker development of exploits would lag behind patch deployment. However, recent advances in AI-driven vulnerability discovery have shattered these assumptions. The April 2026 disclosures, including the Linux kernel patch for Copy Fail and high-profile breaches at Vercel (April 19) and Canvas (May 1), illustrate a new reality where vulnerabilities at the trust boundary are exploited almost immediately after patches are public. These cases underscore a shift from kernel-level bugs to application-layer flaws, which are less protected by traditional defenses.
“Recent breaches point to vulnerabilities in trust boundaries, which are less protected by existing security measures.”
— Vercel security spokesperson
Unclear Impact of AI-Driven Exploits on Future Patching
While evidence indicates that AI accelerates exploit development, it remains uncertain how widespread or persistent these rapid exploits will become across different platforms and vulnerabilities. The long-term effectiveness of existing patching strategies and the potential for new defensive measures are still being evaluated. Additionally, the full scope of the recent breaches and their relation to the collapse of the traditional disclosure window are still under investigation.
Next Steps for Cybersecurity Strategies and Policy
Security experts and organizations are expected to prioritize continuous monitoring, automation, and real-time threat detection to counteract the rapid exploitation enabled by AI. Policymakers may also reconsider disclosure frameworks and incentivize faster, more proactive security practices. Further research will likely focus on developing defenses that address trust boundary vulnerabilities and reduce reliance on traditional patching cycles. The industry will also closely monitor the ongoing impact of recent breaches to adapt security protocols accordingly.
Key Questions
What does the end of the 90-day window mean for cybersecurity?
It signifies that attackers can now develop and deploy exploits faster than before, reducing the effectiveness of traditional patching timelines and requiring new defensive strategies.
Are all vulnerabilities now exploitable immediately after patch release?
Not all, but advances in AI make it increasingly feasible for attackers to rapidly analyze patches and develop exploits, especially for high-value or trust boundary vulnerabilities.
What types of vulnerabilities are most affected by this change?
Vulnerabilities related to trust boundaries, such as OAuth scopes, SaaS integrations, and environment handling, are now more vulnerable to immediate exploitation than kernel memory bugs.
How should organizations respond to these developments?
Organizations should enhance real-time monitoring, adopt automated security tools, and focus on securing trust boundaries and application-layer defenses to mitigate rapid exploit risks.
Source: ThorstenMeyerAI.com