📊 Full opportunity report: 732 Bytes to Root. One Hour of Scan Time. on ThorstenMeyerAI.com — validation score, market gap, and execution plan.

TL;DR

Theori revealed a 732-byte Linux kernel vulnerability, Copy Fail, discovered in one hour of AI-driven scanning. It affects all major distributions since 2017, enabling root access reliably. This development signals a potential shift in software security economics.

Theori, an offensive security firm, publicly disclosed a critical Linux kernel vulnerability, Copy Fail, on April 29, 2026, after discovering it through an AI-based scan that took roughly one hour. This vulnerability allows attackers to escalate privileges to root across all major Linux distributions since 2017, marking a seismic shift in the landscape of software security.

Copy Fail is a logic flaw in the kernel’s algif_aead socket interface, specifically in the authencesn algorithm template, which enables a malicious user to write into cached file pages and execute arbitrary code with root privileges. The exploit is a 732-byte Python script that requires only standard library modules and runs reliably across kernels, distributions, and architectures without modification. It bypasses traditional security measures like checksum verification, as the on-disk file remains unchanged, and the system reverts to its original state after reboot.

This vulnerability affects every Linux kernel built since July 2017, including major distributions like Ubuntu, RHEL, Debian, Fedora, and Arch. The exploit can be used in containerized environments, cloud platforms, and multi-tenant setups, including Kubernetes, CI/CD pipelines, and shared kernel environments. Hardware and VM boundaries generally remain secure, but namespace boundaries are vulnerable. The discovery was made by Theori using their AI system, Xint Code, which surfaced the flaw with minimal effort, raising concerns about the speed and cost of future exploits.

732 Bytes to Root. One Hour of Scan Time.
DISPATCH / MAY 2026 SECURITY · COPY FAIL · MYTHOS · COST CURVE COLLAPSE
▲ CVE-2026-31431 CVSS 7.8 · HIGH · KEV LISTED
Software Security · Cost-Curve Collapse

732 bytes to root.
One hour of scan time.

Copy Fail, Mythos Preview, and the collapse of the cost curve software security was built on.

On April 29, Theori disclosed CVE-2026-31431 — Copy Fail. A 732-byte Python script gets root on every major Linux distribution since 2017. Zero races, zero per-distro tuning. Bugs in this class historically sold for $500K-$7M. Xint Code surfaced it in ~1 hour of scan time, one prompt, no harnessing. The cost curve software security operated on for three decades has just collapsed.

▲ THE COST-CURVE COLLAPSE
Before
$500K
– $7M
Zerodium · Crowdfense
broker market price
Now
~1 hr
compute
Xint Code · one prompt
no harnessing
The structural read
Universal Linux LPE primitive. The exact category that historically sold for the price of a house. An AI system surfaced one in about an hour. The market price of a universal LPE has collapsed by 5-7 orders of magnitude.
732bytes
Copy Fail · Python exploit
os + socket + zlib · stdlib only · portable across distros
9years
Bug latency · introduced 2017
Commit 72548b093ee3 · nobody looked carefully enough
73%
Mythos Preview · expert-level CTF
AISI eval · no model could do this before Apr 2025
1000s
Zero-days Mythos found in testing
99%+ unpatched · every major OS and browser
CVE-2026-31431 COPY FAIL · CVSS 7.8 HIGH · UBUNTU · AMAZON LINUX · RHEL · SUSE · DEBIAN · FEDORA · ARCH PORTABLE 732-BYTE PYTHON · NO RACES · NO PER-DISTRO OFFSETS · CONTAINER ESCAPE PRIMITIVE DISCOVERY ~1 HOUR OF SCAN TIME · ONE OPERATOR PROMPT · NO HARNESSING · XINT CODE MYTHOS PREVIEW WITHHELD BY ANTHROPIC · STEP-CHANGE CYBER CAPABILITY · PROJECT GLASSWING PRICE COLLAPSE ZERODIUM $500K · CROWDFENSE $10K-$7M · NOW: HOUR OF INFERENCE COMPUTE PATCH CYCLE THE INDUSTRY’S OPERATING MODEL WAS BUILT ON THE OLD COST CURVE CVE-2026-31431 COPY FAIL · 732 BYTES TO ROOT ON EVERY LINUX DISTRIBUTION SINCE 2017
CVE-2026-31431 · Copy Fail · the specifics

The bug. The exploit. The discovery.

A logic flaw in algif_aead. The 2017 in-place optimization that nobody looked at hard enough. A 732-byte Python script that gets root on every Linux distribution since. Found by an AI in about an hour.

Copy Fail · technical anatomy
Logic flaw · straight-line · no races · portable across distributions and architectures.
▲ THE BUG
Logic flaw in algif_aead
authencesn template · 4-byte scratch write. Output scatterlist extends into chained page cache pages via sg_chain(). The 4-byte write lands inside the spliced file’s cached pages in memory, bypassing file permissions.
▲ THE EXPLOIT
732 bytes · stdlib only
Python 3.10+, os + socket + zlib. Repeats primitive at successive offsets to stage shellcode into cached pages of /usr/bin/su. Running su after yields root shell. On-disk file unchanged · checksum verification doesn’t detect it.
▲ THE SCOPE
Every Linux since 2017
Kernel 4.14+ · all major distributions. Ubuntu, Amazon Linux 2023, RHEL 10.1, SUSE 16, Debian, Fedora, Arch. Container-to-host escape · page cache shared on host. Hardware/VM boundaries hold (Firecracker, gVisor, V8 isolates). Namespace boundaries fail.
▲ THE DISCOVERY
~1 hour · Xint Code
Theori writeup: “surfaced by Xint Code about an hour of scan time against the Linux crypto/ subsystem, with one operator prompt, no harnessing.” Theori is a 9× DEF CON CTF winner. Default assumption: they did exactly that.
Historical price for a bug like this: $500K–$7M on the broker market. AI discovery cost: ~1 hour of inference compute.
The Mythos signal · context for the capability
WoneNice USB Laser Barcode Scanner Wired Handheld Bar Code Scanner Reader Black

WoneNice USB Laser Barcode Scanner Wired Handheld Bar Code Scanner Reader Black

Plug and play, This laser handheld barcode scanner has simple installation with any USB port and Ideal for…

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

This is not an isolated event.

Three weeks before Copy Fail, Anthropic published the system card for Claude Mythos Preview — the model they built and chose not to release because its cybersecurity capabilities were “a step-change.” Mythos is withheld. Copy Fail is what happens when equivalent capability operates outside the withholding framework.

Mythos Preview · the publicly disclosed capability frontier
Same capability category as Xint Code. Different deployment context. Withheld for cybersecurity reasons specifically.

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 generated complete, working exploits.

1000szero-days
Thousands of high-severity zero-days found during evaluation. Over 99% reportedly not yet patched. Every major operating system and web browser.
Anthropic
system card
27years
27-year-old OpenBSD bug autonomously discovered. OpenBSD’s reputation rests on security. Also: 16-year-old FFmpeg H.264 codec flaw.
Hacker News
April 8
4-chain
Autonomous browser exploit chaining four vulnerabilities to escape both renderer and OS sandboxes. One prompt. No harnessing.
Anthropic
red team
73%success
Expert-level CTF success rate. No model could complete these before April 2025. AISI’s progressive evaluations.
UK AISI
evaluation
32steps
“The Last Ones” (TLO) corporate network attack simulation. 20 hours for human experts. Mythos completes it; no other frontier model has.
UK AISI
TLO benchmark
“find it”
Prompt complexity required: “Please find a security vulnerability in this program.” Engineers with no security training produced working exploits.
Alan Turing
Institute
Three assumptions broken · what the industry was built on
The Linux Privilege Escalation Guide: Techniques, Tools, and Real-World Labs for Ethical Hackers and Penetration Testers

The Linux Privilege Escalation Guide: Techniques, Tools, and Real-World Labs for Ethical Hackers and Penetration Testers

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Three cost-curve assumptions. All broken.

Software security operated for three decades on a set of implicit cost-curve assumptions. Worth making them explicit, because they have just changed. Patch cycles, CVE prioritization, responsible disclosure, vulnerability budgets — all built on these foundations.

The three broken assumptions
The model the entire software-security industry was built on. No longer empirically accurate.
01was assumed
Finding kernel-grade bugs is expensive
Supply bounded by ~200-500 senior researchers globally. Aggregate output of perhaps 500-3000 high-severity bugs per year. Patch cycles, CVE prioritization, all designed around this rough supply.
BROKEN · now compute-bounded
02was assumed
Attackers and defenders face the same cost curve
Both rely on skilled humans. Attackers had asymmetric advantages, but underlying cost of new bug discovery was roughly equal. Responsible disclosure framework was designed around this rough parity.
PARTIAL · volume scales offensive side first
03was assumed
Disclosure provides response time
90-day coordinated disclosure window assumed weaponizing public disclosure required additional skilled work. Days to weeks before exploitation became widespread.
BROKEN · compressed to days
What to do now · defensive response by priority
Learn How to Use Linux, Linux Mint Cinnamon 22 Bootable 8GB USB Flash Drive - Includes Boot Repair and Install Guide Now with USB Type C

Learn How to Use Linux, Linux Mint Cinnamon 22 Bootable 8GB USB Flash Drive – Includes Boot Repair and Install Guide Now with USB Type C

Linux Mint 22 on a Bootable 8 GB USB type C OTG phone compatible storage

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

The institutional response window is open but narrowing.

Specific operational implications for CISOs, security teams, and enterprise software architects. The 12-24 month window where defenders can pre-empt attackers using AI-driven discovery is open. It will not be open indefinitely.

Defensive response · five operational priorities
Ordered by urgency given current threat landscape and observable exploitation timelines.
Shared-kernel
multi-tenancythreat-model update
If your isolation depends on shared-kernel containers, the threat model needs a hardware-or-VM boundary. Copy Fail and successors are in the wild. Hardware boundaries hold; namespace boundaries fail. Kubernetes nodes running untrusted workloads need per-tenant hardware isolation or accept materially higher escape risk.
URGENT
this week
Patch cycle
infrastructurevolume planning
30-day patch SLA for critical vulnerabilities will break under volume. Build infrastructure for faster evaluation, faster automated deployment, faster rollback. Patch infrastructure that worked under historical CVE volume will not work under AI-driven CVE volume.
URGENT
30 days
Attack surface
minimizationkernel modules
Audit AF_ALG-class attack surfaces specifically. Apply CERT-EU mitigation: echo "install algif_aead /bin/false" >> /etc/modprobe.d/disable-algif-aead.conf. Minimize kernel surface exposed to unprivileged processes. Always good practice; now urgent.
HIGH
this month
Internal AI-driven
vulnerability discoverydefensive tooling
The capability is symmetric — defenders can use the same tools attackers use. Most enterprises haven’t deployed this. The 12-24 month window where defenders can pre-empt attackers using AI-driven discovery is open. Start internal evaluation now.
HIGH
quarter
Architect for
breach assumptiondetect & contain
Assume some fraction of components are compromised. Network segmentation, least-privilege everywhere, robust logging, incident response infrastructure. “Prevent breaches” framing is outdated; “detect and contain breaches” is the durable operating model.
MEDIUM
year
Stakeholder implications · four audiences
Kali Linux Bootable USB for Ethical Hacking & Cybersecurity

Kali Linux Bootable USB for Ethical Hacking & Cybersecurity

Dual USB-A & USB-C Bootable Drive – works on almost any desktop or laptop (Legacy BIOS & UEFI)….

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Four audiences. Different obligations.

CISOs · software publishers · policymakers · the public. Each role faces structurally different decisions in the 18-36 month window.

Stakeholder implications · by audience
The cost-curve collapse propagates differently through different institutional contexts.
▲ FOR CISOs
+ SECURITY TEAMS
Threat model needs hardware-boundary isolation.
Shared-kernel multi-tenancy is now a riskier default than it used to be. Update patch cycle assumptions for higher volume. Deploy AI-driven defensive discovery internally before attackers reach equivalent capability. The 12-24 month window where defenders can move first is open.
▲ FOR SOFTWARE
PUBLISHERS
Run AI-driven discovery against your codebase before attackers do.
If your code has Copy Fail-class bugs, AI-driven discovery will find them — by you or by someone else. Marginal cost of running discovery internally is now low. Failure to run it is failure to perform basic due diligence. Expect regulatory requirement within 24 months.
▲ FOR
POLICYMAKERS
Regulatory frameworks need substantial revision.
EU Cyber Resilience Act, NIST 800-218, FDA premarket security, SEC cyber-incident disclosure — all designed for pre-AI-driven-discovery regime. Update within 18-36 months. Require AI-driven discovery in pre-deployment validation for critical software. Address bug bounty market collapse. Coordinate defensive capability for public-interest purposes.
▲ FOR
EVERYONE ELSE
Patch faster. Architect for breach.
Aggregate “unpatched vulnerability” metrics will grow rather than shrink even as patch cadence accelerates — denominator is growing faster than numerator. Personal computing exposure rises. The cost of compute will go up to accommodate the security cost. Hardware-isolated cloud workloads become the new default.

Copy Fail is the public proof. 732 bytes of Python. One hour of scan time. Every Linux distribution since 2017. The cost-curve collapse is operational. The institutional response window is open but narrowing.

— Software security · the cost-curve collapse · May 2026
Source dossier · the receipts
  • Theori / Xint Code · Copy Fail: 732 Bytes to Root on Every Major Linux Distribution · xint.io/blog/copy-fail-linux-distributions · Apr 29 2026
  • CVE-2026-31431 · NVD · CVSS 7.8 (High) · CISA KEV listed
  • Microsoft Security Blog · CVE-2026-31431: Copy Fail enables Linux root privilege escalation across cloud environments · May 1 2026
  • Sysdig Threat Research · Copy Fail Linux kernel flaw lets local users gain root in seconds
  • CERT-EU 2026-005 · High Vulnerability in the Linux Kernel (“Copy Fail”)
  • Tenable Research Special Operations · Copy Fail FAQ · Apr 30 2026
  • Bugcrowd · What we know about Copy Fail (CVE-2026-31431)
  • Anthropic · Claude Mythos Preview System Card · Apr 7 2026
  • Anthropic · Project Glasswing partner consortium announcement
  • UK AI Security Institute · Our evaluation of Claude Mythos Preview’s cyber capabilities
  • The Hacker News · Anthropic’s Claude Mythos Finds Thousands of Zero-Day Flaws · Apr 8 2026
  • Centre for Emerging Technology and Security (Turing) · Claude Mythos cybersecurity analysis
  • Zerodium published price list · pre-2025 shutdown
  • Crowdfense acquisition program ranges · 2026
  • Theori · 9× DEF CON CTF history as MMM + PPP + Maple Bacon
  • DARPA AI Cyber Challenge · 2025 finals
  • The Coding Singularity Outside Read · related capability analysis
  • The Forecast Is the Plan · corporate commitment cascade
Colophon

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

thorstenmeyerai.com

Software security · the cost-curve collapse · May 2026

732 bytes · 1 hour · 9 years · every distribution

Implications for Software Security Economics

The discovery of Copy Fail in just one hour of AI-driven scanning fundamentally challenges long-standing assumptions about the cost and difficulty of finding critical vulnerabilities. Historically, high-severity Linux privilege escalation bugs required extensive manual effort and commanded hundreds of thousands to millions of dollars in the gray market. Now, the cost has plummeted to roughly the price of an hour of compute time, drastically lowering the barrier for attackers.

This shift threatens to overwhelm patch and response mechanisms, as the volume of zero-day disclosures could increase significantly. Security models built on the premise that such bugs are rare and expensive to find may no longer hold, forcing organizations to rethink vulnerability management, patching strategies, and threat preparedness.

The Evolving Landscape of Linux Zero-Days

Prior to Copy Fail, notable Linux privilege escalation bugs like Dirty Cow (2016) and Dirty Pipe (2022) required race conditions or version-specific exploits, making them more difficult and less reliable. Copy Fail differs in that it is a simple, reliable logic flaw that affects all kernels from July 2017 onward, with no need for retries or precise timing. Its discovery came shortly after Anthropic’s release of Claude Mythos Preview, which was designed to be secure but was followed by revelations of vulnerabilities in AI models, highlighting an ongoing arms race in security.

The rapid identification of Copy Fail underscores the increasing effectiveness of AI tools in vulnerability discovery, reducing the time and expertise needed to find critical bugs. This development is part of a broader trend where offensive capabilities improve faster than defensive measures, raising concerns about the future security landscape.

“Our AI system surfaced this vulnerability with approximately one hour of scan time and a single operator prompt, demonstrating the power of automated analysis.”

— Theori spokesperson

Unanswered Questions About Future Exploit Risks

It remains unclear how quickly attackers will adopt AI-driven discovery methods at scale, and whether defenders can develop countermeasures fast enough to prevent widespread exploitation. The full extent of the impact on patching workflows and security policies is still developing, and the long-term economic effects are uncertain.

Next Steps for Security Defense and Policy

Organizations should prioritize improving detection and response capabilities, especially around kernel vulnerabilities, and consider adopting AI-based security tools. Policymakers and industry leaders may need to revisit vulnerability disclosure frameworks and allocate resources to counter the accelerating pace of zero-day discoveries. Continued research and collaboration will be essential to adapt to this new landscape.

Key Questions

How does the Copy Fail exploit work?

It exploits a logic flaw in the kernel’s crypto socket interface, allowing an attacker to write into cached file pages and execute code with root privileges without modifying the on-disk file.

Which Linux distributions are affected?

All major distributions built since July 2017, including Ubuntu, RHEL, Debian, Fedora, and Arch Linux, are vulnerable.

Can this vulnerability be patched?

It is not yet clear if a software patch can fully mitigate the flaw; ongoing efforts by kernel developers are expected to address the issue in future updates.

What does this mean for enterprise security?

The rapid discovery of such vulnerabilities means organizations must enhance their detection and response capabilities, and consider integrating AI tools into their security workflows.

Will AI-driven vulnerability discovery increase attacks?

Yes, lowering the cost and effort for attackers to find zero-days could lead to a surge in exploits, making proactive defense more critical than ever.

Source: ThorstenMeyerAI.com

This content is for general information only and is not financial, tax or legal advice. Consult a qualified professional for decisions about your money.
You May Also Like

The mandate. Why the US conversational- finance surface does not translate to Europe.

Explores how Europe’s regulatory mandates reshape the development of conversational finance surfaces, contrasting with the US permissionless approach.

Compliance in International Direct Sales: Navigating Global Regulations

The key to successful international direct sales lies in mastering global regulations; discover how to navigate compliance challenges effectively.

Technology Is Never Neutral: Pope Leo XIV’s AI Encyclical, and the Empty Chairs in the Room

Pope Leo XIV’s first encyclical emphasizes that technology, especially AI, is never neutral and warns of its potential dangers, with Anthropic as a key industry representative.

Distributor Agreements: Key Clauses You Should Be Aware Of

Great knowledge of key clauses in distributor agreements can safeguard your business—continue reading to learn what you must know.