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

TL;DR

A new Linux kernel vulnerability, dubbed Copy Fail, was publicly disclosed after Theori’s AI system found it in about an hour. The exploit is highly reliable across distributions and architectures, drastically lowering the cost to find and exploit such bugs.

On April 29, security firm Theori publicly disclosed CVE-2026-31431, a Linux kernel privilege escalation bug that can be exploited with a 732-byte Python script, enabling attackers to gain root access within seconds. This discovery, made by AI-driven analysis in roughly one hour, marks a significant shift in the cybersecurity landscape due to its simplicity and universality.

Theori’s Xint Code AI system identified the Copy Fail vulnerability by scanning the Linux crypto subsystem with minimal input, requiring only one operator prompt and about an hour of compute time. The bug resides in the kernel’s algif_aead interface, specifically in the authencesn algorithm, allowing an attacker to bypass file permissions by manipulating cached pages in memory. The exploit involves a straightforward, logic flaw that does not rely on race conditions or version-specific quirks, making it portable across all Linux kernels since July 2017 and affecting major distributions such as Ubuntu, RHEL, Debian, Fedora, and others. The exploit code is minimal—just 732 bytes—and runs on standard Python 3.10+ environments, requiring no recompilation or specialized harnessing. The vulnerability’s scope extends to containerized environments, including Kubernetes, CI/CD pipelines, and shared cloud environments, where page cache sharing enables container-to-host escapes. Hardware boundaries, however, remain secure, and cloud services like AWS Lambda and Firecracker microVMs are unaffected due to their isolation mechanisms.

Compared to previous Linux privilege escalation bugs like Dirty Cow and Dirty Pipe, Copy Fail is notable for its simplicity, reliability, and the absence of race conditions or version dependencies. Its discovery underscores the rapid evolution of AI-driven vulnerability detection, which can now identify highly impactful bugs in a fraction of the time traditionally required. The vulnerability was surfaced by Theori’s system, which analyzed the kernel’s crypto subsystem with minimal effort, highlighting the potential for AI to fundamentally alter vulnerability discovery and exploitation dynamics.

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
Learning Kali Linux: Security Testing, Penetration Testing & Ethical Hacking

Learning Kali Linux: Security Testing, Penetration Testing & Ethical Hacking

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
Amazon

Python script for privilege escalation

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
Learning eBPF: Programming the Linux Kernel for Enhanced Observability, Networking, and Security

Learning eBPF: Programming the Linux Kernel for Enhanced Observability, Networking, and Security

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 demonstrates that the cost of finding critical Linux vulnerabilities has plummeted from hundreds of thousands or millions of dollars to roughly the cost of an hour of AI compute. This collapse in the cost curve challenges longstanding assumptions in cybersecurity, which relied on the idea that such bugs were rare and expensive to find. As AI tools become more capable of identifying zero-days rapidly and reliably, the volume of potential exploits will likely increase, stressing patching infrastructures and security policies worldwide. For enterprise security leaders, policymakers, and software developers, this signals an urgent need to reevaluate risk models, vulnerability management strategies, and defensive investments to keep pace with the growing offensive capability.

Background of Linux Kernel Privilege Escalation Trends

Historically, Linux privilege escalation bugs like Dirty Cow (2016) and Dirty Pipe (2022) required complex conditions such as race conditions or version-specific exploits, making them costly and difficult to discover. These bugs often demanded multiple attempts and precise tuning, which limited their widespread exploitation. The emergence of Copy Fail, with its straightforward logic flaw and universal applicability, signals a paradigm shift. The vulnerability was found within a relatively obscure part of the kernel’s crypto API, yet it affects all major distributions since 2017. Its discovery was facilitated by AI-driven scanning, which can analyze vast codebases rapidly, a capability that was previously infeasible for human researchers. The recent release of Anthropic’s Claude Mythos Preview, a large language model, coincides with this trend, as it hints at an era where AI models can assist in both discovering and understanding vulnerabilities at scale.

“Our system identified this bug with just an hour of scan time and a single operator prompt, demonstrating the power of AI in security research.”

— Theori spokesperson

Unresolved Questions About Exploit Deployment and Defense

While the technical details of the Copy Fail exploit are well-understood, it remains unclear how widely and quickly malicious actors will adopt this technique. The speed at which exploit code will be weaponized and integrated into malware or attack frameworks is uncertain. Additionally, the effectiveness of current patching and mitigation strategies against such a universal and reliable vulnerability is still being evaluated. The impact on cloud providers and container ecosystems depends on how quickly security updates are deployed and whether defenses can be adapted to detect or block such in-memory manipulations.

Expected Developments in Response and Mitigation Strategies

Security vendors and Linux distributions are expected to prioritize patches and kernel updates to mitigate Copy Fail. Researchers will likely analyze the exploit’s mechanics further, potentially developing detection signatures or runtime protections. Meanwhile, AI tools for vulnerability discovery will continue to improve, possibly identifying more such bugs rapidly. Policymakers and enterprise security teams will need to reassess vulnerability management frameworks and prepare for a potential influx of zero-day disclosures facilitated by AI-driven discovery. The next 12 to 24 months will be critical in establishing whether defenses can keep pace with offensive capabilities.

Key Questions

How does the Copy Fail exploit work?

The exploit manipulates cached pages in the Linux kernel’s crypto API, bypassing permissions and allowing execution of malicious code with root privileges. It is achieved through a simple logic flaw that does not depend on race conditions or version-specific behavior.

Which Linux distributions are affected?

All major Linux distributions built since July 2017 are vulnerable, including Ubuntu, RHEL, Debian, Fedora, Arch, and SUSE. Container environments sharing page caches are also at risk.

Can this vulnerability be patched?

Yes, kernel patches are expected to be released promptly by maintainers. However, the widespread use of the bug means many systems may remain vulnerable until updates are applied.

What does this mean for enterprise security?

The rapid discovery of high-impact bugs by AI tools reduces the time window for patching, increasing the risk of exploitation. Enterprises need to enhance monitoring and response strategies to cope with the increased volume of potential zero-days.

Will AI-driven vulnerability discovery become the norm?

Given the efficiency demonstrated by Theori’s system, AI-driven discovery is likely to become a standard part of security research, fundamentally altering the economics and dynamics of vulnerability management.

Source: ThorstenMeyerAI.com

You May Also Like

AMÁLIA · The Three Hard Questions.

Portugal’s €5.5M AMÁLIA project, a European Portuguese LLM, faces key structural questions about openness, native data, and objectives, impacting national AI policy.

The Earnings Call Gap: What Q1 2026 Just Told Us About AI ROI

Analysis of Q1 2026 earnings shows a widening gap between AI investment claims and actual financial results, signaling market skepticism.

Dating App Safety: Quick Checks Before You Meet

Always verify profile details and photos to stay safe; discover essential tips before your first meet-up.

The Enforcement Countdown: 89 Days Until the EU AI Act’s GPAI Penalty Phase Begins

In 89 days, the EU will activate enforcement powers for GPAI providers under the AI Act, enabling fines up to €35 million or 7% of turnover.