📊 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 reporting and patching security vulnerabilities has expired without any vendor notices. Experts warn this shift benefits attackers, as AI tools can now exploit vulnerabilities faster than defenses can respond.
The 90-day window for responsible disclosure of security vulnerabilities has officially closed without any notices from affected vendors, marking a significant shift in cybersecurity practices. This development, confirmed by industry sources, indicates that the traditional advantage held by defenders is eroding, with attackers now able to exploit vulnerabilities faster than patches can be issued.
Historically, the 90-day coordinated disclosure window, established by initiatives like Google Project Zero in 2014, provided a structured period for vendors to patch vulnerabilities after they were reported by researchers. During this window, defenders could deploy patches before malicious actors weaponized the flaws. However, recent developments in AI-driven vulnerability discovery have disrupted this balance.
In April 2026, a security patch for the Linux kernel addressing the ‘Copy Fail’ vulnerability was committed on April 1. Public disclosure occurred on April 29, but during the four-week window, AI tools capable of monitoring kernel commits and analyzing diffs could reconstruct exploits in minutes—much faster than traditional reverse engineering. Experts warn this means attackers can now discover and weaponize vulnerabilities before vendors even issue notices.
Additionally, recent breaches at Vercel and Canvas highlight a shift in the types of vulnerabilities exploited. Instead of memory safety bugs, attackers are targeting trust boundary failures, such as OAuth scope misconfigurations and third-party app permissions, which are less protected by existing defensive measures. These vulnerabilities are often in the integration seams, not the core kernel, and are more accessible to AI-driven discovery.
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.
software patch management 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.
network security monitoring devices
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.
AI cybersecurity defense tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Implications of the Disappearance of the Disclosure Window
This shift fundamentally alters the cybersecurity landscape. With the 90-day window effectively dismantled, defenders lose their primary advantage of deploying patches before attackers can weaponize vulnerabilities. The rise of AI tools capable of rapid exploit development means threats are now immediate and more widespread. This change increases the urgency for organizations to enhance their security measures at the application and integration levels, where traditional defenses are less effective.
Evolving Threats and the Breakdown of Traditional Disclosure
Since the early 2000s, the responsible disclosure framework relied on a mutual understanding: researchers would report vulnerabilities, and vendors would have a limited window to patch before public disclosure. This balance aimed to give defenders a head start. However, recent advancements in AI, exemplified by tools like Theori’s Xint Code, have drastically shortened or eliminated this window. The April 2026 Linux kernel patch is a case in point, where AI can reconstruct exploits from commits in minutes, not days or weeks.
Prior to this, the security community believed that reverse engineering a patch was a significant barrier to attackers. Now, AI tools have lowered that barrier to near zero, enabling even less experienced actors to develop exploits rapidly. The breaches at Vercel and Canvas further demonstrate that vulnerabilities at the trust boundary are now prime targets, and these are less protected by traditional security measures.
“The 90-day window, once a defender’s advantage, is now effectively a vulnerability window for attackers, thanks to AI-driven discovery.”
— Thorsten Meyer
Unclear Impact on Future Patch and Disclosure Practices
It remains uncertain how vendors will adapt to this new reality. Will new disclosure frameworks emerge? How quickly will organizations implement more robust security measures at the application layer? The long-term effects on cybersecurity norms and regulations are still developing, and industry responses are not yet clear.
Next Steps for Industry and Security Practices
Organizations should reassess their security strategies, especially around trust boundaries and third-party integrations. Vendors may need to develop faster patching cycles or alternative disclosure methods. Industry groups are likely to explore new frameworks to address the accelerated threat landscape. Monitoring AI-driven exploit techniques will become essential for proactive defense.
Key Questions
What does the end of the 90-day window mean for cybersecurity?
It means attackers can now exploit vulnerabilities faster than vendors can patch and disclose, reducing defenders’ ability to respond proactively.
Why are trust boundary vulnerabilities becoming more prominent?
Because modern breaches, like those at Vercel and Canvas, show that vulnerabilities at integration points are easier to exploit and less protected by traditional defenses.
How are AI tools changing vulnerability discovery?
AI can analyze code commits and patches in minutes, reconstruct exploits rapidly, and even generate working exploits without formal security training.
What can organizations do to protect themselves now?
Organizations should strengthen security at trust boundaries, monitor AI-driven exploit techniques, and consider faster patching and more dynamic security frameworks.
Source: ThorstenMeyerAI.com