📊 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 effectively closed, as no notices or patches were sent within the period after a major Linux kernel bug was committed. This shift is driven by AI-driven vulnerability discovery, which enables attackers to exploit bugs before patches are publicly available, altering the cybersecurity landscape.
The 90-day coordinated disclosure window for the Linux kernel vulnerability known as Copy Fail has officially closed without any notices or patches from vendors or researchers, marking a significant shift in cybersecurity dynamics. This development underscores how AI-driven vulnerability discovery is transforming traditional defense mechanisms and attack timelines, making this a critical moment for cybersecurity stakeholders.
On April 1, 2026, a patch for the Linux kernel vulnerability dubbed Copy Fail was committed. Despite the patch being public from the moment of commit, no security notice or patch was issued by vendors or researchers during the subsequent four-week period, which traditionally serves as a window for responsible disclosure. This period has historically provided defenders time to deploy patches before attackers could exploit the bug.
However, recent advances in AI-driven vulnerability detection, exemplified by tools like Theori’s Xint Code, enable attackers to monitor kernel commits in real-time, analyze diffs, and develop exploits within minutes. As a result, the window of opportunity for defenders has shrunk dramatically, and the concept of a ‘responsible’ 90-day window is no longer valid. Experts warn that this change favors attackers, who can weaponize bugs before patches are publicly available.
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
Linux kernel vulnerability detection 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 cybersecurity monitoring 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.
cybersecurity vulnerability scanner
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 development fundamentally alters the cybersecurity landscape, shifting the advantage from defenders to attackers. The collapse of the traditional disclosure window means that vulnerabilities can be exploited immediately after they are committed, reducing the time defenders have to respond. It also highlights how AI tools are lowering the barrier for attackers, enabling even less skilled actors to identify and exploit bugs rapidly. This change increases the urgency for organizations to rethink their security strategies and adopt AI-aware defenses.
Evolving Security Practices in the AI Era
Since the early 2000s, the responsible disclosure model relied on a 90-day window, allowing vendors time to patch vulnerabilities before they were publicly disclosed. This framework was based on assumptions that reverse engineering patches took significant time, and that attackers needed additional time to develop exploits after public disclosure. However, in 2026, AI-driven tools can analyze patches and commits instantly, reconstruct exploits within minutes, and monitor code repositories continuously. The Linux kernel’s Copy Fail bug exemplifies this shift, with the patch released on April 1 but potentially exploitable immediately due to AI monitoring.
Recent incidents, including breaches at Vercel and Canvas, reveal that the most critical vulnerabilities now often lie at trust boundaries—such as OAuth scopes and SaaS integrations—rather than kernel memory safety bugs. These vulnerabilities are less protected by traditional defenses and more susceptible to AI-facilitated discovery and exploitation.
“The collapse of the 90-day window signifies a paradigm shift, where AI tools enable attackers to exploit vulnerabilities before defenders can respond.”
— Thorsten Meyer
Unresolved Questions About Future Security Dynamics
It remains unclear how widespread the immediate exploitation of the Copy Fail bug has been, and whether other vulnerabilities are similarly being exploited in real-time. The extent to which vendors and organizations can adapt their detection and patching processes to the AI-driven landscape is also still uncertain. Additionally, the long-term implications of trust-boundary vulnerabilities taking precedence over memory-safety bugs are still emerging, with ongoing debate about necessary defensive innovations.
Next Steps for Security Stakeholders in a Post-Window Era
Security teams and vendors are expected to accelerate AI integration into their monitoring and patching workflows. Researchers may shift focus toward trust-boundary vulnerabilities and supply chain security. Policymakers and industry groups might consider revising disclosure frameworks to account for the rapid pace enabled by AI tools. Monitoring of exploit activity and further case studies of breaches like Vercel and Canvas will shape future best practices. The next 12-24 months will be critical for adapting to this new paradigm.
Key Questions
What does the end of the 90-day window mean for organizations?
It means organizations must enhance their real-time monitoring and response capabilities, as vulnerabilities can be exploited immediately after discovery without waiting for patches or disclosures.
How does AI-driven discovery change the role of security researchers?
AI tools now enable even non-expert actors to identify and exploit vulnerabilities quickly, reducing the traditional advantage held by skilled security researchers and reverse engineers.
Are there any defenses against AI-facilitated exploitation?
Defenses are evolving to include AI-aware detection systems, continuous monitoring, and rapid patch deployment, but the landscape remains highly dynamic and challenging.
What vulnerabilities are now most concerning?
Trust boundary flaws, such as OAuth scope misconfigurations, SaaS-to-SaaS authentication issues, and environment-variable abuse, are now among the most critical vulnerabilities, surpassing traditional memory-safety bugs.
Source: ThorstenMeyerAI.com