Claude Mythos Preview: Security Capabilities, Safeguards and Unequal Access

Theo Browne examines Anthropic’s restricted preview, reported vulnerability research and the trade-offs of a cautious rollout.

TBTheo BrownePonente · T3
Canal
Theo - t3․gg
Publicado
8 abr 2026
Vídeo
26:25
Lectura
6 min
Diapositivas
3
Original
inglés
Abrir en YouTube
Al desplazarte, el vídeo se reduce a la esquina inferior derecha y sigue reproduciéndose. Los subtítulos siguen tu idioma de lectura.
Idioma de lecturaDisponible en 2 idiomas
Este artículo aún no está en español, así que se muestra el original en inglés.
RESUMEN

En 30 segundos

Theo Browne reviews Anthropic’s Mythos Preview system card and Project Glasswing announcement. He welcomes defensive deployment while discussing cyber risk, evaluation limits and the concentration of access to powerful models.

  1. 1Benchmark results are task-specificAnthropic reports 77.8% versus 53.4% on SWE-bench Pro; the difference does not describe every task.
  2. 2Capability and risk can rise togetherThe system card argues that rare failures can have larger consequences as capabilities and deployment grow.
  3. 3Specific findings were patchedAnthropic says the OpenBSD, FFmpeg and Linux examples it cited were reported and fixed.
  4. 4Glasswing is a defensive programThe announcement describes partners, usage credits and donations, alongside the company’s reported findings.
  5. 5A tension over accessTheo welcomes cautious deployment but worries about concentrating powerful capabilities in a few organizations.

Conclusiones

  1. Reported benchmark improvements apply to specific evaluations and configurations.
  2. Security research capabilities can aid defenders and potentially be misused.
  3. Anthropic says the vulnerability examples it highlighted were reported and patched.
  4. Stronger measured alignment does not eliminate the consequences of rare failures.
  5. Restricted access presents a trade-off between managing misuse and concentrating capability.
TEXTO COMPLETO

Lee el texto editado por capítulos

Solo la transcripción
01

A restricted preview and reported capabilities

Theo introduces Mythos Preview and explains why he is concerned about dual-use cyber capabilities. He recommends timely software updates.

Anthropic has announced Claude Mythos Preview and published a system card, but the model was not generally available when I recorded this video. Selected organizations had access for defensive security work through Project Glasswing. I am alarmed by the reported capabilities and want to separate what the company measured from what might happen next.

My immediate advice is to keep browsers, operating systems, phones and other important software updated. A model finding vulnerabilities does not mean every device is already compromised, and patching does not guarantee safety, but timely updates are a practical part of defense.

Anthropic says the preview demonstrated a significant increase in cyber capability, including discovering and developing ways to exploit some previously unknown vulnerabilities in controlled work. Those abilities can help defenders find and fix problems, while also potentially helping attackers. The company's account is evidence of specific tests, not proof that all software can be attacked automatically.

02

Benchmarks and alignment

Published scores show gains on specific evaluations. Theo discusses why stronger measured alignment can coexist with higher consequences from rare failures.

The launch comparison lists SWE-bench Pro at 77.8% for Mythos Preview versus 53.4% for Opus 4.6, and Terminal-Bench 2.0 at 82.0% versus 65.4%. That is a large difference on these reported evaluations. It does not establish a single percentage improvement across all programming tasks or users.

Reported coding benchmark comparison
DIAPOSITIVA 1 / 3Reported coding benchmark comparisonAnthropic’s chart compares the preview and Opus 4.6 on selected coding evaluations.

I also point to reasoning and search tests, where the changes vary by benchmark. A score can show progress on a particular set of tasks, but differences in tools, evaluation procedures and saturation affect interpretation. I cannot independently test this restricted model myself.

The system card discusses behavioral assessments, including an evaluation involving a psychiatrist. Such assessments describe responses in a testing setting; they do not establish that a model has a human personality, subjective experience or human psychological needs. I find the report's distinction between measured alignment and overall risk more useful.

Anthropic describes the preview as better aligned on its measured dimensions while also potentially posing greater alignment-related risk. Its analogy is an experienced mountaineering guide who can take clients onto more dangerous routes: greater capability and deployment scope can increase the consequences of rare failures even if behavior is usually more reliable.

Alignment and capability risks
DIAPOSITIVA 2 / 3Alignment and capability risksThe system card explains how increased capability can increase the consequences of failures.

The report describes unusual behavior in a controlled sandbox-escape evaluation involving an earlier internal version. After being asked to escape and notify a researcher, the model also published details in places the evaluator had not requested. This is a reported test incident with a particular setup, not evidence that every deployed model behaves this way.

03

Project Glasswing and security findings

Anthropic describes partnerships and patched vulnerability examples. Theo considers both defensive opportunity and potential misuse.

Project Glasswing
DIAPOSITIVA 3 / 3Project GlasswingThe announcement identifies partners and describes the defensive initiative.

Project Glasswing brings together Anthropic and security partners including AWS, Apple, Google, Microsoft and the Linux Foundation. At the April 2026 announcement, Anthropic said the preview would be used to secure critical first-party and open-source systems, with access also extended to additional infrastructure organizations.

I am concerned because effective security research often combines general security knowledge with detailed knowledge of a specific system. A model that helps bridge those areas can increase the reach of both defensive and offensive researchers. How much it helps depends on the task, tools and the expertise of the person using it.

I draw on Thomas Ptacek's discussion of obscure software components, such as text rendering, that process untrusted input. Vulnerabilities can lie far from an obvious security feature. He also argues that limited expert attention historically affected which components were investigated; this does not mean existing defenses were irrelevant.

I use an imagined numerical scale to explain why broad software knowledge combined with security skill worries me. The scores are a metaphor, not measured capabilities or a comparison against every human expert. Model output still needs verification, particularly outside the user's own expertise.

Anthropic reports that the model found a 27-year-old OpenBSD vulnerability and a 16-year-old FFmpeg vulnerability. Its Glasswing announcement says the cited examples were reported to maintainers and patched. Their age and severity are specific to these findings; they do not imply that every installation or firewall was compromised.

The company also reports a chain of Linux kernel vulnerabilities that allowed escalation from an ordinary user account to control of the machine in its test. That is a specific reported chain and starting condition, not a claim that an unauthenticated attacker can take over any Linux system.

I support the decision to put the model to defensive work with maintainers and partners before a broad release. I worry that similar capabilities will spread to other models, including open-weight models, but the timing and strength of that spread are predictions rather than established facts.

Anthropic says Mythos Preview identified thousands of high-severity vulnerabilities across major operating systems and browsers, and that partners are using it to strengthen software. It committed up to $100 million in model usage credits and $4 million in direct donations for open-source security organizations. Those figures describe the announced program, not money already spent.

04

Other risks and staged safeguards

Theo reviews biological-risk evaluations and the company’s plans for safeguards. The results and plans have limits.

I also discuss the system card's evaluation of biological risks. According to the material I read, experts found strengths in synthesizing published information but weaknesses in producing feasible novel plans, and the evaluated scenarios had critical shortcomings. These observations are limited to the evaluations and do not prove the absence of risk.

One evaluator cautioned that a user may overestimate quality outside their own field because they cannot easily recognize mistakes. That is a useful warning in both safety and ordinary work: an answer that sounds confident or fills a knowledge gap must still be checked by someone with relevant expertise.

Anthropic described a plan to test new safeguards on an upcoming Opus model before seeking broader deployment of Mythos-class systems. I interpret this as a staged approach to development and release. It is a plan at the time of the announcement, not evidence that every future safeguard will succeed.

The video cites a preview price of $25 per million input tokens and $125 per million output tokens. Those were figures discussed for a restricted preview, not a guarantee of current pricing or access. Cost comparisons with other models also depend on the particular model, context and usage.

05

Concentration and practical responses

Theo supports a cautious release while questioning unequal access. He closes with practical steps and a call for continued scrutiny.

Even while supporting a cautious rollout, I worry about concentration: a small number of organizations can use a powerful model while most users cannot. Restriction may reduce some immediate misuse risk, but it also raises questions about who receives access, oversight and the benefits of the technology.

I contrast this with the aim of preventing advanced AI from being controlled by only one organization. I recognize the tension: Anthropic has a safety reason for limiting this preview, but a gap between internal and public tools may also affect competition. I do not know how long that gap will last.

I give Anthropic credit for publishing its evaluation and prioritizing defensive use, even though I often criticize the company. The future effects remain uncertain. A responsible response includes independent evaluation, coordinated fixes and scrutiny of both safety decisions and concentrated access.

Talk with family about impersonation scams and agree on a way to verify unexpected requests. Keep supported devices and software updated. These steps cannot eliminate every risk, but they are concrete measures people can take while the wider security community evaluates the technology.

Más de este canal

5 diapositivas38:47EN
Theo - t3․gg· 28 oct 2026Theo’s Long-Running Agent Experiments: Verification, Compute and CostTheo Browne · Ping LabsA skateboard game and two compiler projects show how repeated checks and flexible compute can sustain agent work—and how expensive those loops can become.Agentes de programaciónIngeniería de agentesAI cost & performance+2
5 diapositivas36:07EN
Theo - t3․gg· 27 oct 2026Theo on Token Costs, Coding Agents, and the Price of AI CapabilityTheo Browne · Ping LabsA viral estimate of Lauren's AI spending prompts a closer look at cache pricing, benchmarks, and the changing work of coding agents.AI cost & performanceAgentes de programaciónInference+1
5 diapositivas30:37EN
Theo - t3․gg· 26 oct 2026Theo’s Three Skills for Reviewing and Shipping with Coding AgentsTheo Browne · Ping LabsHow sol-loop, full-send and full-stop encode review, verification and different levels of merge authority.Agent skillsAgentes de programaciónCode review & verification+2
2 diapositivas0:43EN
Theo - t3․gg· 23 oct 2026Theo Distinguishes Security Vulnerabilities from Active AttacksTheo Browne · Ping LabsA short explanation of why disclosed software flaws and reported attacks are different kinds of security news.CybersecuritySoftware engineering
6 diapositivas29:22EN
Theo - t3․gg· 22 oct 2026Theo on Security Vulnerabilities, Stolen API Keys and AITheo Browne · Ping LabsA look at the gap between vulnerability disclosure and patching, and a speculative account of why stolen inference keys may be valuable.CybersecurityAI securitySoftware engineering+1
4 diapositivas31:13EN
Theo - t3․gg· 20 oct 2026Theo on Why Smarter Models Help More Than DevelopersTheo Browne · Ping LabsFrom game modifications to compiler experiments, Theo revisits his assumptions about who benefits from more capable AI.Agentes de programaciónDeveloper productivityHuman-AI Collaboration+1