Modelspublished

Anthropic Gives Enterprise Teams Mythos 5’s Bug Hunt, Not Its Prompt Box

The public beta broadens access to a cyber-capable model, but keeps the critical control point intact: customers can receive vulnerability findings, not direct instructions to the model.

By 4 min read
Anthropic Gives Enterprise Teams Mythos 5’s Bug Hunt, Not Its Prompt Box

Listen to this story

The audio brief

About 1:31
0:001:31
Read transcript
Anthropic is giving Enterprise customers access to Claude Mythos 5 for vulnerability scans—but not to Mythos 5 itself. Teams connect a GitHub repository in the admin console, and the model runs in the background, returning findings and suggested patches instead of opening an interactive prompt. The feature is now in public beta through Claude Security. Mythos 5 can trace behavior across files, read Git history, and check its own findings through an adversarial verification step. Each result includes a Common Weakness Enumeration category, confidence and severity ratings, plus a proposed patch. But the control line is clear: every patch still needs human review and approval before deployment. If engineers want to implement it in Claude Code on the web, they use the models already included in their account—not Mythos 5. Scans draw from existing Enterprise-plan tokens, with listed pricing of ten dollars per million input tokens and fifty dollars per million output tokens. Anthropic says the design follows testing with roughly fifty Project Glasswing partners, who reported more than ten thousand high- or critical-severity vulnerabilities. The company is also offering a thirty-five-million-dollar Defender Advantage Fund in Claude credits for organizations securing open-source software, while exploring Mythos integrations in partner cybersecurity products. The immediate question is whether these fixed-output scans produce findings strong enough to justify the human triage still required before anything reaches production.

Story brief

3 key points

Anthropic is broadening access to Claude Mythos 5 through a constrained Claude Security beta for Enterprise customers, not by offering the model as a general chatbot. Repository scans can trace cross-file behavior, verify findings, and propose patches, while teams retain review and deployment responsibility. Usage draws from existing plan tokens, with listed pricing of $10 per million input tokens and $50 per...

  1. 01

    Admins enable scans in the Enterprise console; repository analysis is billed against existing plan tokens rather than a separate Mythos add-on.

  2. 02

    Findings include CWE category, confidence, severity, and suggested patches; human approval remains mandatory before deployment.

  3. 03

    Mythos 5 is not available in Claude Code or an interactive prompt; implementation uses models already included in the account.

Enterprise teams can now send GitHub repositories to Claude Security for vulnerability analysis powered by Claude Mythos 5. They do not get a Mythos 5 chat window: the system returns findings and suggested patches inside a constrained scanning product.

The feature is in public beta for Claude Enterprise customers. An administrator enables it in the admin console, and scans are billed as standard token usage under the organization’s existing plan rather than through a separate model add-on.

That makes Mythos available for one defined task, rather than as a general interactive capability. The distinction is central to the rollout: the same system that can inspect code for flaws is not exposed as a model users can freely steer.

The scan replaces the prompt box

A user connects a repository and Mythos 5 runs in the background. Anthropic says the scan traces data flows across files and reads Git history; each surfaced finding includes a Common Weakness Enumeration category, confidence rating, severity rating, and suggested patch. Anthropic also says the model challenges its own findings through an adversarial verification step before they are shown.

The boundary continues after a finding appears. Teams can open Claude Code on the web to implement a patch, but that interactive work uses the models already available in their account, not Mythos 5. The scan does not extend Mythos access to other surfaces.

A wider route out of a restricted program

Anthropic had limited Mythos 5 to a vetted-partner program since April. The company says roughly 50 Project Glasswing partners using Claude Mythos Preview found more than 10,000 high- or critical-severity vulnerabilities, giving the new beta a prior defender-focused testing ground rather than a wholly new use case.

The Enterprise release changes who can invoke the scan, but not the product’s fixed-output design. That leaves a practical question for customers: whether the model’s stated cross-file analysis and verification process produce findings that justify the human triage required before a fix reaches production.

The intended targets are high-severity flaws

Anthropic says Claude Security is aimed at memory corruption, injection flaws, authentication bypasses, and cross-file logic errors. Those categories frame the product as a code-review and triage tool, not an automated patching system.

Operational options inside the scan workflow

  • Teams can limit a scan to a directory or schedule scans for recurring review.
  • Findings can be sent to Slack or Jira through webhooks, or exported as CSV or Markdown.

There is still a cost boundary alongside the access boundary. Scans consume Enterprise-plan tokens, and Mythos 5 is listed at $10 per million input tokens and $50 per million output tokens. Anthropic has not turned the model into a separate Enterprise add-on, but repository analysis is not presented as a free service.

The rollout extends beyond Enterprise scans

Anthropic also announced the $35 million Defender Advantage Fund, which offers Claude credits to organizations securing open-source software. It is working to embed Mythos 5 in partner cybersecurity products and services, where users would receive purpose-built outputs rather than the model itself.

Anthropic also plans to expand its Cyber Verification Program to broader dual-use capabilities on Opus and Sonnet, with Mythos-class access to follow. For now, the Enterprise beta leaves teams responsible for judging scan results and approving any patch before it reaches production.

Editorial analysis

Our Read

Our read: Anthropic is testing whether a product boundary can be a meaningful safety boundary. A repository scan is useful precisely because it narrows the interaction to a defender’s workflow, but its value will depend on whether security teams find the results reliable enough to change triage and remediation. The next evidence to watch is adoption through the Enterprise beta and partner tools, alongside whether the planned Cyber Verification expansion creates a clearly governed route for broader access. The approach resembles Thinking Machines’ argument that access can widen in stages while providers retain the ability to monitor and revoke it.

Sources

  1. marktechpost.comAnthropic Brings Claude Mythos 5 to Claude Security: Enterprise Teams Get Frontier Vulnerability Scanning Without Direct Model Access