📊 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 90-day coordinated disclosure period has expired without any vendors issuing notices or patches. This shift in vulnerability management raises questions about the future of responsible disclosure and security response times.
The 90-day coordinated disclosure window, a cornerstone of cybersecurity practices since the early 2000s, has officially closed without any notices or patches from affected vendors, marking a significant shift in vulnerability management.
On April 1, 2026, a critical Linux kernel vulnerability known as Copy Fail was patched in the mainline kernel. Despite the patch being publicly available from that date, no vendor or affected organization issued a security notice or deployed a patch within the subsequent 28 days, which ended on April 29, 2026.
This absence of notices is notable because the traditional 90-day window was designed to give defenders time to respond while limiting attacker opportunities. The delay or absence of vendor disclosures suggests a fundamental change in how vulnerabilities are managed, especially with AI-driven tools capable of rapidly analyzing patches and developing exploits.
Security researchers and industry observers are now questioning whether the responsible disclosure model remains effective in its current form, given the accelerated pace of vulnerability discovery and exploit development facilitated by AI technologies.
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 device
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.
vulnerability disclosure software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Implications of the Disclosed Window Closure
The expiration of the 90-day window without vendor notices indicates a potential shift where attackers may gain an advantage over defenders. The traditional model relied on the assumption that patches would be deployed promptly, and that the window between patch release and exploitation was manageable.
With AI systems capable of monitoring commits, reverse-engineering patches in minutes, and developing exploits rapidly, the period of vulnerability has effectively shortened to zero. This could lead to more widespread, faster exploitation of vulnerabilities, especially in critical infrastructure and cloud services.
Furthermore, the lack of vendor disclosures raises concerns about transparency and accountability, as organizations may remain unaware of vulnerabilities until they are exploited in the wild, increasing risk exposure across sectors.
Evolving Practices in Vulnerability Disclosure
The responsible disclosure framework was established over two decades ago to balance the interests of researchers and vendors, with the 90-day window serving as a negotiated compromise. It was predicated on assumptions that no longer hold in 2026.
Recent high-profile breaches, such as those involving Vercel and Canvas, demonstrate that many of the most critical vulnerabilities today are not memory-safety bugs but trust boundary failures at integration points like OAuth scopes and SaaS-to-SaaS communication. These vulnerabilities often remain undetected by traditional security measures and are exploited rapidly once discovered.
Meanwhile, AI-driven discovery tools, like those used by Theori and Anthropic, can surface zero-day vulnerabilities and develop exploits within minutes of a patch being released, rendering the traditional 90-day window obsolete.
“The collapse of the knowledge floor and the rapid development of exploits by AI tools mean the traditional 90-day window is no longer a defender’s advantage.”
— Thorsten Meyer
Unclear Impact on Future Security Practices
It remains uncertain whether vendors will begin to adopt more proactive disclosure or if new frameworks will emerge to address the accelerated pace of vulnerability discovery driven by AI. The long-term implications for cybersecurity policy and industry standards are still developing.
Next Steps for Vulnerability Management and Policy
Security industry leaders and policymakers are likely to reevaluate disclosure standards, possibly moving toward more transparent or real-time notification systems. Organizations should prepare for faster threat timelines and consider adopting AI-based monitoring tools to identify vulnerabilities proactively.
Further research and discussion are expected to clarify how to balance responsible disclosure with the realities of AI-enabled exploitation, shaping the future of cybersecurity protocols.
Key Questions
What does the end of the 90-day window mean for cybersecurity?
It suggests that vulnerabilities could be exploited more rapidly after discovery, reducing the time defenders have to respond and patch, especially as AI tools accelerate exploit development.
Why have vendors not issued notices for the recent Linux kernel patch?
It is not yet clear whether vendors are intentionally withholding notices, are unaware of the implications, or are reevaluating their disclosure strategies in light of AI-driven attack capabilities.
How does AI change the landscape of vulnerability discovery?
AI can analyze patches, reverse-engineer vulnerabilities, and develop exploits within minutes, collapsing traditional windows of opportunity for defenders.
Will the responsible disclosure model be replaced?
It is uncertain. Industry experts are debating whether new models or regulations are needed to address the accelerated pace of vulnerability discovery and exploitation.
What should organizations do now?
Organizations should enhance their monitoring capabilities, adopt AI-driven security tools, and prepare for faster response times to emerging vulnerabilities.
Source: ThorstenMeyerAI.com