📊 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 reporting and patching security vulnerabilities has closed without any vendor notices. AI’s ability to discover exploits rapidly is reshaping traditional disclosure timelines, raising new security challenges.

The 90-day responsible disclosure window has officially closed without any notices from vendors, signaling a significant shift in cybersecurity dynamics driven by AI’s rapid vulnerability discovery capabilities.Traditionally, the 90-day window established by the responsible disclosure framework allowed vendors time to patch vulnerabilities after they were reported by researchers. However, in 2026, this window has effectively become a vulnerability itself, as AI systems can now analyze patches and commits within minutes, reconstruct exploits, and weaponize bugs before patches are widely deployed. The recent case involves the Linux kernel patch for the Copy Fail vulnerability, committed on April 1, 2026, which was publicly disclosed by Theori on April 29. During the four-week window between commit and disclosure, AI tools could have identified and exploited the bug, which was already reconstructible from the diff. This development challenges the fundamental assumptions underpinning the traditional 90-day window, which relied on humans taking days to weeks to analyze patches and develop exploits. Experts warn that this rapid exploitation capability diminishes the defender’s advantage and shifts the threat landscape towards attackers with AI-powered tools. Additionally, recent breaches at Vercel and Canvas reveal that the most critical vulnerabilities are no longer memory-safety bugs but trust boundary failures at integration points, which are less protected by conventional defenses. These cases underscore that the most impactful vulnerabilities now reside in SaaS integrations, OAuth scopes, and third-party permissions, areas where defensive infrastructure is weaker and AI-driven discovery is more effective.
The 90-Day Window Closed. Nobody Sent a Notice.
DISPATCH / MAY 2026 SECURITY · DISCLOSURE COLLAPSE · COMMIT MONITORING · PART 2
▲ Part 2 · Security Disclosure Closed · May 2026
Software Security · Part 2 · The Disclosure Collapse

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 THREE ASYMMETRIES · ALL FAVOR THE ATTACKER NOW
Asymmetry 01
Time
90-day window collapses to diff-to-exploit minutes. Distribution lag becomes the structural vulnerability window.
Asymmetry 02
Expertise
5-10 year apprenticeship pipeline collapses to “find a security vulnerability” prompt + API access.
Asymmetry 03
Category
Memory safety → trust-boundary composition. Defensive infrastructure built for the wrong layer.
Defender disadvantage compounds across all three. Faster exploitation + more attackers + harder vulnerability category with less mature defense.
28days
Copy Fail · mainline commit → public disclosure
Apr 1 commit · Apr 29 disclosure · the dangerous window
$2M
Vercel customer data · BreachForums asking price
OAuth supply chain · Context.ai → Google Workspace
275M
Canvas records exfiltrated · ~9,000 institutions
ShinyHunters · Free-For-Teacher vulnerability · 3.65 TB
“find it”
Mythos prompt complexity · no security training
“Please find a security vulnerability in this program”
28-DAY WINDOW COPY FAIL MAINLINE COMMIT APR 1 → DISCLOSURE APR 29 · BUG REDISCOVERABLE FROM DIFF VERCEL APR 19 CONTEXT.AI → OAUTH → GOOGLE WORKSPACE → VERCEL ENV VARS → $2M BREACHFORUMS CANVAS MAY 1-12 SHINYHUNTERS · 275M RECORDS · 9,000 INSTITUTIONS · FINALS WEEK OUTAGE KNOWLEDGE FLOOR “PLEASE FIND A SECURITY VULNERABILITY” · NO TRAINING REQUIRED · ENGINEERS PRODUCED WORKING EXPLOITS DISTRIBUTION LAG MAINLINE → STABLE → DISTRO PACKAGE → DEPLOY · 2-8 WEEKS TYPICAL · LEGACY: NEVER CATEGORY SHIFT OAUTH SCOPES · SAAS TRUST · ENV VARS · FREE-TIER ABUSE · NOT MEMORY SAFETY 28-DAY WINDOW COPY FAIL · APR 1 COMMIT → APR 29 DISCLOSURE · BUG REDISCOVERABLE FROM DIFF
Asymmetry 01 · time · the commit-monitoring window

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.

Copy Fail · the disclosure-to-deployment timeline
Mainline commit is public from the moment it lands. Distribution propagation takes 2-8 weeks. AI processes the diff in minutes.
Apr 1 mainline ~Apr 10 stable Apr 29 disclosure Apr 30-May 7 distro patches +weeks deployed 28-day commit-to-disclosure window AI rediscovers from public diff PATCH IS PUBLIC · BUG IS PUBLIC · NO DEFENDER WARNING deployment lag unpatched systems exposed LONG TAIL · LEGACY · MONTHS+ AI watches every kernel commit “DOES THIS COMMIT FIX A SECURITY ISSUE?”
Apr 12026
Mainline commit lands. Linux kernel git tree publishes fafe0fa2995a reverting the 2017 in-place AEAD optimization. Patch is now public.
PUBLIC
INSTANT
~Apr 102026
Stable kernel backports. Greg KH’s stable trees include the patch. Still: no distribution package yet · no end-user deployment.
STABLE
TREES
Apr 292026
Public disclosure by Theori. CVE-2026-31431 announced. Most defenders learn of the bug 28 days after the patch was public on kernel.org.
CVE
PUBLIC
Apr 30 → May 72026
Distribution packages. Ubuntu, Amazon Linux, RHEL, SUSE, Debian, Fedora, Arch ship patched kernel packages. Each on its own schedule.
PACKAGES
AVAILABLE
+weeks → +months2026
End-user deployment. 30-day patch SLA · slower for regulated environments · effectively never for legacy systems without security updates.
DEPLOYED
SLOWLY
The 90-day window assumed private patches. Open-source patches are public from minute zero. The framework is misaligned with the capability landscape.
Asymmetry 02 · expertise · the knowledge floor collapse
Generative AI-Powered Assistant for Developers: Accelerate software development with Amazon Q Developer

Generative AI-Powered Assistant for Developers: Accelerate software development with Amazon Q Developer

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.

The knowledge floor · before AI / now
Who can do vulnerability research. Pool of capable actors expands by orders of magnitude.
▲ Before · 2015-2023
Senior researcher path
  • 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
▲ Now · 2026
API access + one prompt
  • 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.

— Alan Turing Institute · CETaS · Claude Mythos cybersecurity analysis
Asymmetry 03 · category · where the bugs actually live
Cute-Patch It Works on My Machine Meme Embroidered Iron on sew on Patch Funny Emblem Programmer Humor

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.

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.

Two case studies · April-May 2026
No memory corruption. No kernel exploit. Trust-boundary composition failures. Mature defensive infrastructure for memory safety doesn’t apply here.

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.

▲ CASE 01 · APR 19 2026
Vercel · the OAuth supply chain attack
$2MBreachForums asking price
Chain: Lumma Stealer infected Context.ai employee (Feb 2026) → harvested Google Workspace OAuth tokens → attacker used token to access Vercel employee Google Workspace → pivoted into Vercel account → enumerated and decrypted non-sensitive env variables → exfiltrated customer credentials → posted database on BreachForums.
Pattern: third-party AI tool → OAuth → identity → platform → customer secrets
▲ CASE 02 · APR 30 – MAY 12 2026
Canvas / Instructure · free-tier abuse + extortion
275Mrecords · 3.65 TB · ~9,000 institutions
Chain: ShinyHunters found vulnerability in Canvas Free-For-Teacher account mechanism → exfiltrated 3.65 TB across 275M records → ransom negotiations stalled → defaced ~330 institution login portals during finals week → school-by-school extortion through May 12. Names, emails, student IDs, private inbox messages exposed.
Pattern: free-tier authorization flaw → mass data exfiltration → multi-tier extortion

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.

Operational response · four audiences
Practical Vulnerability Management: A Strategic Approach to Managing Cyber Risk

Practical Vulnerability Management: A Strategic Approach to Managing Cyber Risk

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.

Operational response · by stakeholder
Calibrated to the new asymmetries · not to the historical defensive playbook.
▲ FOR CISOs
+ SECURITY TEAMS
Monitor upstream commits. Compress patch SLAs.
Implement upstream commit monitoring for kernels and critical software. Subscribe to mainline security lists. Evaluate suspicious commits with internal AI tooling. Target 72-hour deployment for kernel patches, 7-day for major apps, 14-day for everything else. Audit OAuth permission landscape. Treat SaaS supply chain as tier-1 infrastructure.
▲ FOR SOFTWARE
PUBLISHERS
Your commits document where your bugs are.
Security-shaped commits are findable by AI. Move toward private bug coordination for high-severity findings. Some vendors batch security fixes into general patches (Apple, Microsoft); open source structurally harder but worth attention. Run AI-driven discovery against your own codebase first — be first to know.
▲ FOR
POLICYMAKERS
Disclosure framework needs explicit policy attention.
Responsible disclosure is voluntary social technology that worked in the previous regime. Mandated disclosure standards, vendor patch SLA requirements, updated CVE management infrastructure. Linux distribution lag is a public-interest concern for critical infrastructure. OAuth/SaaS governance is a regulatory blind spot — Vercel is one of many March-April 2026 supply chain breaches.
▲ FOR
EVERYONE ELSE
Two-factor everything. Watch your OAuth grants.
Authenticator apps, not SMS. Passkeys where available. Aggressive credential rotation. Assume your SaaS providers will be breached — have a rotation playbook. Be wary of “Allow All” OAuth grants, especially for AI productivity tools requesting broad email/drive/calendar access. The Vercel chain started here.

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.

— Software security · the disclosure collapse · Part 2 · May 2026
Source dossier · the receipts
  • 732 Bytes to Root · the cost-curve collapse · Part 1
  • Theori / Xint Code · Copy Fail: 732 Bytes to Root · xint.io · Apr 29 2026
  • Linux kernel mainline patch · commit fafe0fa2995a · Apr 1 2026
  • CVE-2026-31431 · NVD · CVSS 7.8 (High) · CISA KEV listed
  • Project Zero · 90-day coordinated disclosure policy · 2014
  • Vercel Security Bulletin · April 2026 · vercel.com/kb/bulletin/vercel-april-2026-security-incident
  • Trend Micro · The Vercel Breach: OAuth Supply Chain Attack · Apr 21 2026
  • The Hacker News · Vercel Breach Tied to Context AI Hack
  • TechCrunch · Zack Whittaker · App host Vercel says it was hacked · Apr 20 2026
  • Hudson Rock · Context.ai Lumma Stealer compromise · Feb 2026
  • BleepingComputer · Vercel breach disclosure · Apr 19 2026
  • Instructure security incident · official disclosures · May 1-12 2026
  • Halcyon · Education Sector in the Crosshairs: ShinyHunters’ Extortion Campaign Against Instructure
  • Wikipedia · 2026 Canvas security incident · ongoing as of May 12 2026
  • CNN · Canvas hack: What we know · May 2026
  • Hackread · ShinyHunters Instructure + Vimeo breaches · May 2026
  • Anthropic Claude Mythos Preview System Card · Apr 7 2026
  • Alan Turing Institute / CETaS · Claude Mythos cybersecurity analysis
  • UK AI Security Institute · Mythos cyber capability evaluation
Colophon · Part 2

Set in Source Serif 4, IBM Plex Sans, & IBM Plex Mono. Security-advisory aesthetic. Free to embed with attribution.

thorstenmeyerai.com

Software security · the disclosure collapse · Part 2 of 2 · May 2026

28 days · 275M records · $2M · “find it”

Cybersecurity Threat Monitoring: Preventing Network Fraud with Best Practices

Cybersecurity Threat Monitoring: Preventing Network Fraud with Best Practices

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

The end of the traditional 90-day disclosure window marks a fundamental shift in cybersecurity, reducing the time defenders have to respond to vulnerabilities. AI’s ability to analyze patches and develop exploits within minutes erodes the advantage that responsible disclosure once provided. This change increases the risk of zero-day exploits being weaponized before patches are available, especially at the integration and trust boundary layers where conventional defenses are less effective. As a result, organizations must reconsider their security strategies, emphasizing real-time monitoring and AI-driven detection to keep pace with attackers. The breaches at Vercel and Canvas exemplify how vulnerabilities in SaaS and third-party integrations are now prime targets, further complicating the defensive landscape.

Evolving Cybersecurity Landscape and the Role of AI

Since the early 2000s, the responsible disclosure framework relied on the assumption that analyzing patches and developing exploits took days to weeks. The 90-day window was designed to give vendors time to patch while allowing researchers to disclose vulnerabilities publicly if patches were delayed. However, recent advances in AI, exemplified by tools like Theori’s Xint Code, have drastically shortened this timeline. In April 2026, the Linux kernel patch for Copy Fail was committed, and within days, AI systems could have reconstructed and weaponized the bug. The recent breaches at Vercel (April 19) and Canvas (May 1) further illustrate that the most damaging vulnerabilities are now trust boundary failures in SaaS environments, not traditional memory-safety bugs. These developments reflect a broader shift in attack vectors and defense strategies, emphasizing the need for continuous, AI-enabled security monitoring.

“AI-driven vulnerability discovery is collapsing the traditional 90-day window, turning it into a vulnerability for defenders rather than a safeguard.”

— Thorsten Meyer

Unresolved Questions About Future Security Strategies

It remains unclear how organizations will adapt their security practices to counter AI-enabled rapid exploit development, and whether new frameworks will emerge to replace or supplement responsible disclosure. The long-term impact on patch deployment timelines and the effectiveness of real-time AI defenses is still being evaluated.

Next Steps for Security Stakeholders and Policy Makers

Organizations must enhance their security posture with AI-driven monitoring and incident response capabilities. Policymakers and industry groups are likely to reconsider disclosure norms and develop new standards for vulnerability management in an era where AI accelerates exploit development. Further research and collaboration are needed to establish resilient defenses against AI-enabled threats.

Key Questions

Why did the 90-day disclosure window end without notices?

AI systems can now analyze patches and develop exploits within minutes, rendering the traditional 90-day window ineffective and allowing attackers to weaponize bugs before vendors can patch.

What types of vulnerabilities are most exploited now?

Trust boundary failures at SaaS integration points, OAuth scopes, and third-party permissions are now the most targeted vulnerabilities, rather than memory-safety bugs.

How are organizations responding to this shift?

Organizations are adopting AI-enabled security monitoring and real-time threat detection to keep pace with rapid exploit development, as traditional patching cycles become less effective.

Will responsible disclosure still be useful?

The effectiveness of responsible disclosure is diminishing; new approaches emphasizing continuous monitoring and AI-driven defense are being developed to address the accelerated threat landscape.

What are the risks of not adapting to these changes?

Failure to adapt increases the likelihood of zero-day exploits being weaponized before patches are deployed, leading to more frequent and severe breaches.

Source: ThorstenMeyerAI.com

You May Also Like

The Continual Learning Research Map: Where the Memento Constraint Stands in May 2026

Six months after initial analysis, the Memento Constraint remains a key bottleneck for autonomous AI, with multiple research directions converging but no ready solutions yet.

Social Media Safety: How Oversharing Creates Real-World Risk

Many social media oversharing habits can expose you to serious risks, so understanding how to protect yourself is crucial.

How to Create a Safer Buffer Between Your Public Life and Home Life

Create a safer buffer between your public and home life by setting clear boundaries—discover essential strategies to protect your privacy and maintain balance.

The $9 Billion Signature Tax: How DocuSign’s Business Model Survives on One Assumption

A new open source project, DocuSeal, challenges DocuSign’s dominance by offering a free, self-hosted digital signature solution, revealing vulnerabilities in the industry.