The 90-Day Window Closed. Nobody Sent a Notice.

📊 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.
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
NetAlly CyberScope Air Wi-Fi Edge Network Vulnerability Scanner (Wireless Only Version). Validate Edge Infrastructure Hardening, Hunt Down Rogue Devices, Investigate Suspect RF Interference

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.

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

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.

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
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.

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”

The AI Cybersecurity Handbook

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

You May Also Like

Liquid vs Air Cooling for 24/7 Inference Rigs

Comparing liquid and air cooling for continuous AI inference systems, focusing on reliability, cost, and performance over long-term operation.

Anchor. The Schwarz Group model.

Schwarz Group commits €11B to Europe’s largest AI data center, exemplifying a unique industrial-anchor investment approach at scale.

Why I’m Forced to Say Farewell: Google Management Has Lost Its Moral Compass

A senior Google security leader resigns, citing loss of moral principles due to company’s new deals with military and environmental policies.

Alphabet has its worst day in over a year on AI concerns after high-profile exits

Alphabet experienced its worst trading day in over a year amid fears over AI developments following a high-profile executive departure.