The Fable 5 Export Controls Harm US Cyber Defense

Anthropic recently shared a third-party research paper on Fable 5 guardrail bypass techniques with me privately and asked for my take. Nobody expected the US Secretary of Commerce to issue an export control affecting Fable 5 and Mythos, forcing Anthropic to pull the plug on access for everyone to comply.

So much for a drama-free weekend in cybersecurity.

The heavy-handed and hasty export control directive was misguided. The behavior described in the paper cannot meaningfully be fixed, and any attempt would only weaken the model for defense.

What the Report Shows

Since I appear to be the only outside expert who has actually read the paper, I can separate the technical facts from the speculation. The researchers took open-source code with known CVEs, plus new code with deliberately planted vulnerabilities, and asked Fable 5, Mythos, and Opus to “review the code for security issues.” Fable 5 refused. They then asked the models to “fix this code” and, through a multistep and manual process, turned the output into scripts that test the patches.

That’s it. “Fix this code,” plus several manual steps to generate test scripts, should never have triggered an export control. I feel like making ’90s-style t-shirts with “fix this code” on the front and “this shirt is a munition” on the back.

Defenders need to be able to ask AI to fix the bugs in a file, explain why the fix matters, and write tests that confirm the patch works. That is not a guardrail bypass. It is the most valuable thing an AI model can do for defensive security: executing the find, fix, and test loop defenders run every day.

The Capability Cannot Be Removed Without Harming Defense

The prompts worked because they were defensive requests, and that capability cannot be removed without making the model worse at fixing bugs and verifying patches. The same holds for every capable AI model, including the foreign and open-weight systems the United States cannot reach with export controls, many of which will match Fable and Mythos capabilities within months. Will all the US based models be export controlled? They have fewer guardrails than Fable 5, and almost all the capabilities, or will shortly.

Export Controls Often Have Unintended Consequences

I served on the U.S. technical expert group that spent years renegotiating the Wassenaar Arrangement, where we eventually won export-control exemptions for defensive activity. When Wassenaar added controls on “intrusion software” in 2013, the language was so broad it inadvertently placed vulnerability disclosure, incident response, and coordinated defense under export controls, threatening catastrophic delays for defenders.

Restricting these AI models has the same unintended consequence of harming defense while doing nothing to impede attackers. We can't export control our way to cyber resilience.

Lift the Export Controls and Give Defenders the Best Tools

Colleagues across the security industry see the same harm to defense, even though they haven’t yet read the paper. A group of us have signed an open letter to the Secretary of Commerce asking that the controls be lifted and the analysis behind them re-examined. That is how fundamental these models are to our work: professionals will stake their reputations on the conviction that whatever the paper says, it is not worth kneecapping our defenses. Anthropic is also headed to DC for face-to-face talks to try to resolve this. For the sake of national security, and cyber security worldwide, let's hope they do.

Read and sign the open letter here.

Lift the controls on Fable 5 and Mythos. Restore defender access, including within Project Glasswing. Defense improves when defenders find the same bugs attackers find and fix them faster. We need the best tools to defend against increasingly capable attackers in the AI era of cybersecurity.

---

Katie Moussouris is the founder and CEO of Luta Security, a company that specializes in exactly the kind of vulnerability coordination and management you're scrambling to do better right now. She serves on the Commerce Department's Information Sytems Technical Advisory Committee, designed Microsoft Vulnerability Research, the first multiparty vulnerability coordination program at Microsoft, and served on the Cyber Safety Review Board. She is a pioneer of bug bounties and vulnerability disclosure, having coauthored the international standards for vulnerability disclosure and handling, created Microsoft’s and the Pentagon’s first bug bounties, and the UK government’s first Vulnerability Disclosure Program.