📊 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 ended without any notices from vendors. AI-driven discovery now enables attackers to exploit patches within days, shifting the security landscape.
Vendors and security researchers have confirmed that the 90-day window for responsible disclosure has effectively closed, with no notices or patches issued for recent critical vulnerabilities. This shift enhances attackers’ ability to exploit bugs before defenders can respond, marking a significant change in cybersecurity dynamics.
The 90-day coordinated disclosure framework, established in the early 2000s and popularized by Google Project Zero in 2014, mandated vendors to patch vulnerabilities within 90 days of notification. However, recent developments reveal this window is no longer a defender advantage. AI systems, such as Theori’s Xint Code, can monitor kernel commits and reconstruct exploits within minutes of patch releases, drastically reducing the time attackers have to weaponize vulnerabilities. For instance, the Linux kernel patch for ‘Copy Fail’ was committed on April 1, 2026, and publicly disclosed on April 29, but AI tools could potentially have reconstructed the exploit during the four-week window, exposing a critical vulnerability before patches were widely deployed. Additionally, recent breaches at Vercel and Canvas highlight that the most consequential vulnerabilities now reside in trust boundaries, such as OAuth scopes and SaaS integrations, where traditional defenses like memory safety measures are ineffective. Experts warn this knowledge shift, combined with AI’s capabilities, poses a new, more immediate threat landscape for organizations worldwide.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

NetAlly CyberScope Air Wi-Fi Edge Network Vulnerability Scanner (Wireless Only Version). Validate Edge Infrastructure Hardening, Hunt Down Rogue Devices, Investigate Suspect RF Interference
Portable, handheld form factor – Take it anywhere for on-site security testing. This field-ready tool gives you visibility…
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.

Applied Network Security Monitoring: Collection, Detection, and Analysis
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.

Cute-Patch It Works on My Machine Meme Embroidered Iron on sew on Patch Funny Emblem Programmer Humor
Size: 3 inches tall
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.

The AI Cybersecurity Handbook
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Implications of the Disrupted Disclosure Cycle
The collapse of the 90-day window means attackers can now exploit vulnerabilities almost immediately after patches are released, reducing defenders’ lead time. This accelerates the threat timeline, especially as AI tools enable non-expert actors to develop exploits rapidly. The shift toward trust-boundary vulnerabilities further complicates defenses, as existing security measures focus on memory safety at the kernel level, not on application-layer trust boundaries. As a result, organizations face increased risk of data breaches and service disruptions, with traditional patching and defense strategies becoming less effective. This change demands a reevaluation of cybersecurity practices, emphasizing real-time monitoring and proactive threat detection to adapt to the new environment.Evolving Security Landscape and Past Frameworks
The responsible disclosure model has historically relied on a 90-day window to balance researcher credit and vendor patching. This framework was predicated on the assumption that reverse engineering patches takes significant time and that vendors would deploy patches faster than attackers could exploit them. However, recent advances in AI, such as Theori’s capability to analyze kernel commits instantly, have shattered these assumptions. The Linux kernel’s ‘Copy Fail’ bug, patched on April 1, 2026, illustrates how AI can reconstruct exploits during the disclosure window. The breaches at Vercel (April 19) and Canvas (May 1) demonstrate that modern vulnerabilities often involve trust boundary failures, which are less protected by traditional security measures. These developments mark a fundamental shift in vulnerability discovery, patching, and exploitation timelines, challenging the core principles of responsible disclosure.“Our recent breach revealed that many of the most critical vulnerabilities are in trust boundaries, which are harder to defend with existing memory safety-focused tools.”
— Security researcher at Vercel
Unresolved Questions About Future Security Risks
It is not yet clear how widespread the ability of AI systems to reconstruct exploits truly is across different platforms and vulnerabilities. While the Linux kernel example is well-documented, the extent to which attackers are actively exploiting this capability remains uncertain. Additionally, the long-term effectiveness of new defensive strategies focusing on trust boundaries and real-time detection is still being evaluated. The full impact of the collapse of the disclosure window on global cybersecurity practices is also an ongoing area of analysis, with experts debating how quickly organizations can adapt to this new threat landscape.
Next Steps for Organizations and Security Frameworks
Organizations will need to enhance real-time monitoring and adopt AI-driven threat detection tools to identify exploits immediately after patches are released. Security vendors and researchers are likely to develop new frameworks emphasizing rapid response at the application and trust boundary levels. Policymakers and industry groups may also revisit disclosure standards, possibly moving toward more opaque or controlled disclosure processes to mitigate immediate exploit risks. Further research will focus on assessing the actual exploitation of AI-reconstructed vulnerabilities in the wild and developing countermeasures tailored to this accelerated threat environment.
Key Questions
Why does the collapse of the 90-day window matter?
It means attackers can exploit vulnerabilities immediately after patches are released, reducing the time defenders have to respond and increasing the risk of widespread exploitation.
How are AI systems changing vulnerability discovery?
AI can analyze patches and commits instantly, reconstruct exploits within minutes, and even generate working exploits without expert knowledge, drastically shortening attack timelines.
What types of vulnerabilities are now most concerning?
Trust boundary failures, such as OAuth and SaaS integrations, are now more critical than traditional kernel memory bugs, as they are less protected by existing defense measures.
What should organizations do now?
They should implement real-time monitoring, adopt AI-based detection tools, and focus on securing trust boundaries to mitigate immediate exploitation risks.
Will the responsible disclosure process be replaced?
It is uncertain; some experts suggest new frameworks may emerge, but the current model is fundamentally challenged by AI capabilities and rapid exploit development.
Source: ThorstenMeyerAI.com