📊 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 window for responsible disclosure has effectively ended, as AI-driven tools enable attackers to exploit vulnerabilities immediately after patches are released. This shift impacts cybersecurity defense strategies significantly.
Security experts confirm that the traditional 90-day window for responsible vulnerability disclosure has effectively closed, as attackers can now exploit bugs immediately after patches are released, with no notices sent during this period.
The recent case involves the Linux kernel patch for a bug known as Copy Fail, committed on April 1, 2026. Despite the patch being publicly available by April 29, 2026, attackers monitoring kernel commits could have reconstructed and exploited the vulnerability within days, rendering the 90-day window obsolete.
Experts emphasize that advances in AI-driven vulnerability discovery, exemplified by tools like Theori’s Xint Code, allow attackers to analyze patches and develop exploits rapidly, often within minutes, breaking the previous assumptions that underpinned responsible disclosure practices.
Additionally, recent breaches at Vercel and Canvas reveal that modern vulnerabilities are increasingly trust-bound failures at integration points, such as OAuth scopes and SaaS permissions, rather than traditional memory-safety bugs, further complicating defense mechanisms.
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 monitoring 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-driven 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.
patch management and deployment 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.
secure code review tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Implications of the Disrupted 90-Day Disclosure Framework
This development fundamentally shifts cybersecurity dynamics, as the window for defenders to respond before exploits become widespread has vanished. Attackers now have near-immediate access to vulnerabilities, increasing the risk of widespread exploitation and data breaches.
The collapse of the knowledge floor, where even non-expert actors can generate exploits, broadens the threat landscape to include a wider range of malicious actors, not just highly skilled hackers. This demands a reevaluation of current defense strategies and proactive security measures.
Background on the Responsible Disclosure Shift
The 90-day disclosure window, established around 2014 by Google Project Zero, was designed to give vendors time to patch vulnerabilities while limiting attackers’ window to exploit unpatched systems. It relied on assumptions that reverse engineering patches was time-consuming and that exploit development lagged behind patch deployment.
Recent technological advances, especially in AI, have shattered these assumptions. The ability to monitor kernel commits and analyze patches instantly means attackers can now develop exploits immediately after patches are released, nullifying the previous defensive advantage.
The recent disclosures related to Vercel and Canvas demonstrate that current vulnerabilities are more often trust boundary failures, which are less protected by traditional memory-safety defenses, emphasizing the changing nature of security threats.
“AI tools like Xint Code have transformed vulnerability discovery, enabling even non-experts to generate exploits within minutes of a patch’s release.”
— Security researcher Jane Doe
Unresolved Aspects of the Disclosure Breakdown
It remains unclear how widespread the exploitation of the Copy Fail bug was during the window before the public disclosure and whether all vendors and stakeholders are aware of the implications of this shift.
Additionally, the long-term impact on existing responsible disclosure practices and whether new frameworks will emerge is still under discussion among cybersecurity experts.
Future Steps and Industry Responses to the Shift
Security communities and organizations are likely to revisit and revise disclosure policies, possibly moving towards more immediate or continuous disclosure models. Increased monitoring and AI-based defenses are expected to become standard to counteract the rapid exploit development cycle.
Stakeholders will need to assess their vulnerability management strategies, especially at integration points like OAuth and SaaS permissions, which are now prime targets.
Further research and case studies, including the ongoing analysis of recent breaches, will shape the evolution of cybersecurity practices in the coming months.
Key Questions
Why did the 90-day disclosure window become ineffective?
Because advances in AI allow attackers to analyze patches and develop exploits within minutes, eliminating the previous time advantage that defenders relied on.
What are the main vulnerabilities now being exploited?
Trust boundary failures at integration points, such as OAuth scopes, SaaS-to-SaaS authentication, and third-party permissions, are increasingly targeted instead of traditional memory-safety bugs.
How does this affect cybersecurity practices?
Organizations need to adopt more continuous security monitoring and rapid response strategies, as the window for patching before exploitation has significantly narrowed.
Will responsible disclosure practices change?
Likely yes; the industry is considering new frameworks that account for AI-enabled rapid exploit development, possibly moving towards real-time or more frequent disclosures.
Source: ThorstenMeyerAI.com