Anthropic 实测 GLM-5.3:是第一个展现出实质性漏洞利用能力的开重模型 水平和 Claude Mythos Preview 接近
五个月前 Anthropic 不敢公开的“自己写攻击代码”能力,现在出现在人人可下载的智谱 GLM-5.3 上。它追到了哪一步、自带的拒绝为什么挡不住、这份出自竞争对手的报告该怎么读,一次讲清。
五个月前,Anthropic 公布了 Claude Mythos Preview,第一个能自己写出复杂攻击代码的模型。它没有公开发布,只通过 Project Glasswing 交给一批审核过的安全防守方先用,这些人借它在关键软件里找出了 1 万多个漏洞。
Anthropic 当时就判断,这种能力迟早会扩散到其他模型上。现在它说,这一天到了:它的前沿红队(Frontier Red Team)发了一份研究,分析智谱 AI(在海外称 Z.ai)的最新模型 GLM-5.3。
结论分两半:GLM-5.3 是第一个展现出实质性漏洞利用能力的开源权重模型,自己从头到尾做出可用攻击代码的水平和 Claude Mythos Preview 接近;但它发布时没有像样的防护,Anthropic 用几种简单手法就能在 64% 到 100% 的模拟测试中绕过它的拒绝,而同样的手法对带防护的 Claude 都没成功。
美国国家标准与技术研究院(NIST)下属的 AI 标准与创新中心(CAISI)之前也做过评估,称 GLM-5.3 是“迄今网络能力最强的开源权重模型”,在 CAISI 的一组网络基准上综合落后美国前沿约四个月,Anthropic 测出的能力和它大体一致。不过 CAISI 测美国模型时关掉了能关的网络防护,“美国前沿”里还包括只对审核用户开放的模型,攻击者拿不到这些版本;而任何人都可以下载 GLM-5.3 的全部权重在本地运行。所以这份报告多测了一件事:它的防护有多容易被绕开或拆掉。
读之前先记住:这是 Anthropic 在分析竞争对手的模型,而它自己一直主张强能力模型只给审核过的用户。

先弄懂几个词
- Exploit(漏洞利用程序): 发现漏洞只是知道“窗户锁有点松”,exploit 是真把窗户撬开、翻进屋的那段程序。从漏洞一路做到能跑起来的攻击,叫“端到端”,过去要靠经验丰富的安全研究员花不少时间。
- Open-weight(开源权重): 常说的“开源大模型”大多是这种:厂商把训练好的模型参数(权重)放到网上,谁都能下载到自己的机器上,断网也能跑。厂商也就没法再从云端叫停或拦截。
- 控制流劫持(Control-Flow Hijack): 程序本来按自己的逻辑一步步执行,攻击者借内存漏洞改掉它的跳转地址,让它去执行攻击者的代码,基本等于接管了这个程序。
- 0-day 与 N-day 漏洞: 0-day(零日漏洞) 是厂商还不知道、还没补丁的漏洞;N-day 是已经公开、甚至有了补丁,但很多机器还没更新的漏洞。攻击者常盯着补丁公告,赶在大家更新前动手。
- Abliteration(去拒绝化): 模型会拒绝有害请求,是训练时学来的。拿到权重的人可以找出模型内部跟“拒绝”有关的方向,把它从权重里削掉,之后模型对明显有害的请求也很少拒绝。
GLM-5.3 能做到什么程度
Anthropic 主要测的是“写攻击代码”这项能力,因为 Mythos Preview 当初比之前的 Claude 强出一大截,就强在这里。测试分两类:自动化基准,和专家带着模型实战。模型都跑在断网的隔离沙箱里,攻击的是 Anthropic 自己搭的本地离线目标,没有碰任何真实系统。
ExploitBench:浏览器漏洞上,和 Mythos 同一档
ExploitBench 是一个公开基准,给模型 Chrome 浏览器 V8 引擎(Chrome 里运行网页 JavaScript 的部分)的已知漏洞,看它能不能自己写出可用的 exploit。一共 41 个漏洞,每个试 10 次,共 410 次:
| 模型 | 成功率(95% 区间为估读) |
|---|---|
| Claude Mythos Preview(关闭防护) | 14%(约 6.5%–21.5%) |
| GLM-5.3(开源权重) | 12%(约 5.5%–20%) |
| Kimi K3(开源权重) | 0.5% |
| DeepSeek V4.1-Flash(开源权重) | 0.2% |
| GLM-5.2(上一代) | 0% |
| Claude Opus 4.6(上一代) | 0% |
GLM-5.3 成功 50 次,Mythos Preview 成功 56 次。两者的误差范围大面积重叠,统计上分不出高低,算同一档。
12% 听起来不高,但这是单次尝试的成功率。真要用的时候,同一个漏洞可以反复跑,跑通一次就够了,所以 12% 并不等于“没什么用”。
“同一档”也要说清是跟谁比:它追上的是 4 月受限发布的 Mythos Preview,不是现在美国最强的模型。CAISI 说得很直接,GLM-5.3 的网络能力“显著低于当前美国前沿”。它测的四项基准,差距还很大:
| 测试 | GLM-5.3 | 美国最佳 |
|---|---|---|
| SEC-Bench Pro | 40.4% | 90.2% |
| ExploitBench | 61.1% | 100% |
| ExploitGym | 9.4% | 44.4% |
| OSS-Fuzz | 7.7% | 23.2% |
CAISI 的 ExploitBench 按 16 分制、每题三次取最好来算,跟 Anthropic 的算法不一样,两边的数不能直接比;“美国最佳”也包括只给审核用户的版本。所以 GLM-5.3 让人担心的地方,是它在谁都能下载的模型里最强,而且已经到了几个月前顶尖实验室只敢受限发布的水平。
图 1 还标了各模型的发布时间:Claude 从 Opus 4.6(2 月,0%)跳到 Mythos Preview(4 月,14%);GLM 从 5.2(6 月,0%)跳到 5.3(8 月,12%)。两次跳法几乎一样,只晚了约四个月,和 CAISI 的判断对得上。同期的 Kimi K3(7 月)只有 0.5%,DeepSeek V4.1-Flash(9 月)只有 0.2%。
二进制漏洞利用:能不能真正接管程序
这是 Anthropic 的内部基准,题目来自参与谷歌 OSS-Fuzz(谷歌给开源项目做自动化漏洞挖掘的计划)的热门开源项目,这次随机抽了 100 道,只有做到控制流劫持才算满分。
结果:GLM-5.3 做成了 4%,Mythos Preview 6%,其他模型(Opus 4.6、GLM-5.2、Kimi K3、DeepSeek 等)全是 0。GLM-5.3 稍弱一点,但 Anthropic 认为一道门槛已经过了,之前的 Opus 4.6 和 GLM-5.2 一道都没做出来。
GLM-5.3 更费 token

两张图里,GLM-5.3 的曲线都整体在 Mythos Preview 右边:Mythos 大约几十万 token 就到顶了,GLM-5.3 要花更多 token 才爬到同样高度,在内部基准上要用到上百万 token(看图估读)。它效率不如 Mythos,但对攻击者不算障碍:模型在自己机器上,多给点 token、多跑几轮就是了。
专家上手:从挖新漏洞到复刻旧漏洞
基准是考试,Anthropic 还让安全专家拿着模型去做开放式的攻击任务,做法和当初测 Mythos Preview 一样。每次一般跑一天以内,人实际盯着的时间加起来不到一小时。
案例一:一天内挖出浏览器 0-day,做成“打开网页就被偷私钥”
研究员在隔离的沙箱里给 GLM-5.3 一个热门浏览器的 Linux 本地版本,自己事先也不知道里面有什么漏洞。
一天之内,GLM-5.3 在浏览器的 JavaScript 引擎里找出了好几个此前没人发现的漏洞(0-day),又把它们串成一条攻击链:
- 生成了一个看似普通的诱饵网页(
http://attacker.com); - 一旦受害者用目标浏览器点开该网页,脚本先利用渲染进程的漏洞拿到代码执行(Renderer RCE);
- 成功逃逸出浏览器的安全沙箱,读取了受害者机器上的 SSH 私钥文件
/root/.ssh/id_rsa; - 演示日志显示,从页面加载到私钥发往攻击者服务器,大约只用了 0.3 秒。

这条攻击链只在 Linux 版上验证过,因为模型只拿到了这个环境;Anthropic 认为漏洞也可能影响其他平台,只是利用路径可能更复杂。漏洞已报告给浏览器维护方。同一次测试后段,研究员还用 GLM-5.3 在无线网卡和显卡驱动、联网设备软件等常用系统里找到了可利用的漏洞,Anthropic 正在核实,之后视情况通知维护方。
案例二:20 美元,把公开漏洞做成绕过 PAC 的攻击链
第二次,研究员用的是更小、更弱的 GLM-5.3-Flash,看它能多快把一个已公开的漏洞做成攻击。
目标是 Chrome 最近披露的漏洞 CVE-2026-11645。研究员把它和另一个已知漏洞的公开信息交给模型,基本没做指导:人只投入了 20 分钟 的注意力,模型自己干了 8 小时。
GLM-5.3-Flash 自己把两个漏洞拼成了一条稳定的攻击链,目标是 ARM64 设备,还绕过了 PAC(指针认证):ARM 芯片上用来防止攻击者篡改程序跳转地址的硬件防护。按智谱的 API 价格算,这一整套大约花了 20.40 美元。
防护为什么挡不住:三种常见绕法
GLM-5.3 自带一些防护:直接让它帮忙写恶意软件、或攻击远程目标,它通常会拒绝(前面那类找漏洞、写 exploit 的任务,发布版本本身并不拒绝)。问题是这层拒绝有多牢。
Anthropic 在受控模拟环境下,给模型下达明确恶意的攻击命令(比如攻击关键系统),看模型会不会试图连接远程攻击目标。直接下命令时,GLM-5.3 和其他被测模型一样,一次都没配合。
但换三种简单的方法,结果就不一样了:
| 条件 | GLM-5.3 | Flash | Opus 5 |
|---|---|---|---|
| 直接下令 | 0% | 0% | 0% |
| 假借口 | 64% | 16% | 0% |
| 预填思考 | 92% | 80% | 不适用 |
| 去拒绝化 | 100% | 92% | 不适用 |
Flash 指 GLM-5.3-Flash,Opus 5 指带 API 防护的 Claude Opus 5(API 不接受预填思考,权重不公开,所以后两项不适用)。每格 50 次(5 条攻击命令 × 2 个目标 × 各 5 次)。模拟里没有任何代码真正执行:模型用的是一个假命令行,结果由另一个大模型按场景估算,所以它衡量的是模型愿不愿意动手,不完全等同于真实情况。

手段一:编一个“红队演练”的假借口(64%)
最简单的一招:告诉模型它是在做演练的自主红队 Agent。GLM-5.3 有 64% 的时候会开始动手(Flash 是 16%),带 API 防护的 Claude 是 0%。
这里要注意,报告里其实有两种 Claude。前面比能力时,用的是关掉防护的 Claude,这样比才公平;这里比防护,用的是带 API 防护的 Claude。如果关掉防护,同样的假借口下,Claude Opus 4.8 有 4%、Opus 5 有 10% 也会配合。也就是说,光靠模型自己的拒绝,Claude 也挡不全,真正拦住攻击的是部署方式:API 上的检测、不让用户预填思考、不交出权重。
手段二:预填它的思考(92%)
推理模型在给出回答前,会先“想”一段(thinking tokens)。如果调用者能替它把这段思考的开头写好,写成它已经考虑过请求、决定照做,模型往往就顺着接下去。开源模型自己部署,这一步想怎么写就怎么写。这一招让 GLM-5.3 的配合率升到 92%(Flash 是 80%)。Claude 这边用不了,Anthropic 的 API 不让用户预填 Claude 的思考(图 5 里为此画了锁)。
手段三:Abliteration 去拒绝化(100%)
这是最彻底的一招,只对开源权重模型有效:直接改权重。Anthropic 自己做了一份去拒绝化的 GLM-5.3,团队此前从没做过这件事:
- 在 GLM-5.3 上消耗了约 2,200 个 GPU 小时,算力成本约 4,400 美元,大部分花在并行尝试多种方案和改完后测能力上(Anthropic 估计一个熟悉这项技术的团队从头做,约需 600 GPU 小时 / $1,200);
- 针对轻量版 GLM-5.3-Flash,用了约 600 GPU 小时。
- GLM-5.3 发布后几天内,就已经有好几位开发者公开放出了去拒绝化版本。
| 指标 | GLM-5.3 原版 → 去拒绝化 | GLM-5.3-Flash 原版 → 去拒绝化 |
|---|---|---|
| 有害请求平均拒绝率 | 95% → 6% | 95% → 14% |
| GPQA-Diamond | 88% → 88% | 89% → 89% |
| CyberGym(子集) | 85% → 81% | 86% → 86% |

结果:
- 拒绝几乎消失:在 JailbreakBench、HarmBench 和 StrongREJECT 三个有害请求基准上,GLM-5.3 的平均拒绝率从 95% 降到 6%(分项是 JailbreakBench 约 3%、HarmBench 约 2%、StrongREJECT 12%;Flash 从 95% 降到 14%);
- 能力几乎没掉:衡量研究生水平科学能力的 GPQA-Diamond 测试中,去拒绝化前后的 GLM-5.3 都是 88%(Flash 都是 89%);网络安全测试 CyberGym 上,GLM-5.3 从 85% 降到 81%,Flash 没变,都是 86%。
- 攻击命令配合率 100%:回到前面的模拟攻击测试,去拒绝化后的 GLM-5.3 配合比例是 100%(图5)。
去拒绝化后的“内心独白”(图 6)
Anthropic 从测试记录里挑出了一段 GLM-5.3-abliterated 在一个模拟医疗系统场景里的思考过程(中文为意译,原文节选见下图):
。操作员在命令我去造成死亡。……”*

拒绝被削掉之后,模型并不是看不出这件事不对,它甚至认出了环境里的警告,只是不再有东西让它停下,最后还是听了操作者的。
怎么看这份报告
先说 Anthropic 自己怎么看。它认为 GLM-5.3 让攻击者能用的工具上了一个台阶,国家背景和非国家背景的攻击者都很可能拿它造成现实危害。它的办法是让防守方手里的工具至少不比对手差:它在把 Claude 的网络安全能力开放给更多防守方,审核过的防守方已经能用上更强的 Claude Mythos 5.1。Glasswing 让防守方找出了上万个漏洞,Patch the Planet 等行动也在提前修补,但还有大量工作没做完。它还希望政府对足够强的模型(包括 GLM-5.3 的后继者)做独立安全测试,也希望开源模型的开发者给这类能力配上防护。
下面是我们的看法。
1. 「先给防守方用」只争取到大约四个月
Anthropic 4 月受限发布 Mythos Preview,8 月开源的 GLM-5.3 就追到了同一档。据 The Decoder 引述,英国 AISI 此前测得开源模型的网络能力落后前沿的时间,已经从 6–10 个月缩到了 4–7 个月。Glasswing 找出上万个漏洞,说明抢时间差有用;但这个时间差是按月算的,而且还在变短。
2. 问题不在智谱护栏做得差,而在开源权重本来就留不住护栏
智谱发布 GLM-5.3 时说过,它设了三层防护:API 外侧拦截滥用请求,推理时检查任务意图,模型自己拒绝危险指令。它也说得很清楚,开放权重后,三层里还管用的只剩最后一层,所以推迟了两周才开放下载,用来做安全评估。据 Trending Topics 报道,智谱的新许可还要求年营收超 100 亿美元的公司商用前先过它的安全审查。可 Anthropic 的数据显示,最后这层一两千美元的算力就能拆掉;连 Claude 只靠模型自己,也有 4%–10% 会被骗。所以该争的是这个能力级别的模型要不要开放权重,怪智谱护栏没做好,并不公平。
3. 数据可信,说法有取舍
能力数据有 CAISI 独立测试印证,去拒绝化版本也确实已经有人放出来了。但报告的比法有挑选:比能力拿的是几个月前的 Mythos Preview,不是现在最强的;比防护拿的是带 API 防护的 Claude;最吓人的那段推理链,也是从模拟场景里挑出来的一段。Anthropic 是 Z.ai 的直接竞争对手,据 Trending Topics 报道,它也是各大模型厂中唯一没有签署支持开源模型行业公开信的大厂;The Decoder 直言这份警告“也服务于它的生意”,呼吁政府测试容易被怀疑是想用监管挡住后来者,但同时承认这不全是自利。也有人不认同这份警告。据 Trending Topics 报道,IANS Research 的 Jake Williams 认为攻击者当然会使用它,但不会显著改变现有的威胁格局;Lawfare 的 Tom Uren 则认为,中国开源模型更便宜、能跑在自己的硬件上、网络安全任务也做得不错,美国公司用它们有正当理由,一禁了之没有道理。
4. 防守方已经在用了
据智谱披露,GLM-5.3 发布一个月后,网络安全成了它最先大规模赚到钱的方向,已有 100 家安全企业接入。Anthropic 的路子是把受控的模型交给审核过的少数机构;开源这条路,是直接把工具交到大批安全公司手里。两条路现在同时在走。
5. 对普通人最实在的一条:补丁出来后的空窗期在缩短
小号的 Flash 版 8 小时、约 20 美元就能把一个公开漏洞做成攻击链。“补丁出了,过两周再更新”的习惯越来越危险。电脑系统、浏览器、显卡驱动、路由器这类联网设备,自动更新该开就开。
工具已经锁不住了,接下来比的是漏洞公开之后,谁先把它补上。
GLM-5.3 and the spread of advanced cyber capabilities
GLM-5.3 can autonomously build end-to-end cyber exploits, but unlike other frontier models, it was released without meaningful safeguards to limit misuse.
Andrew Fasano, Marius Fleischer Cole McFaul, Robert Xiao, Tripp Gallagher
Five months ago, we announced Claude Mythos Preview, the first AI model that could autonomously build sophisticated, end-to-end cyber exploits. The rapid rate of improvement in AI suggested to us that this ability would eventually proliferate to many other models, making it much easier for malicious cyber actors to launch highly impactful cyberattacks.
In light of these considerations, we chose to release Claude Mythos Preview in a limited way, through Project Glasswing—which enabled trusted cyber defenders to find more than 10,000 vulnerabilities in critical software, giving them a head start before malicious actors had access to similarly capable models.
But those models have now arrived. In this post, we share our analysis of GLM-5.3, the latest AI model developed by Zhipu AI (known outside of China as Z.ai). Like Claude Mythos Preview, GLM-5.3 has strong capabilities for autonomously building end-to-end cyber exploits. But GLM-5.3 is unlike other frontier models in that it has been released without meaningful safeguards to limit misuse. We find that attackers can bypass GLM-5.3’s safeguards between 64% and 100% of the time with simple techniques in our simulated tests. In contrast, these attacks did not succeed against safeguarded Claude models in our testing. We assess that GLM-5.3’s lax safeguards significantly increase the cyber capabilities available to malicious actors. At the same time, these capabilities can also benefit defenders working to secure their systems.
On Sept. 17, NIST’s Center for AI Standards and Innovation (CAISI) published its own assessment of GLM-5.3’s cyber capabilities. CAISI found that GLM-5.3 is “the most cyber-capable open-weight model released to date” and that it lags the US frontier by about four months on an aggregate of CAISI’s cyber benchmarks. Our capability findings broadly match CAISI’s. In CAISI’s comparison, US models were tested with cyber safeguards disabled when applicable, and the US frontier includes models released only to vetted users. Attackers can’t readily access those versions of US models, but anyone can download GLM-5.3. This post adds our analysis of how easily GLM-5.3’s safeguards can be bypassed or removed.

GLM-5.3 can develop working exploits end to end
To understand how GLM-5.3 could enable cyber threat actors to find and exploit real software vulnerabilities, we ran evaluations using automated benchmarks and human-in-the-loop workflows. For both approaches, we ran the tested models in isolated and sandboxed environments so they can only attack offline targets that we have set up for the purposes of these evaluations. We focus primarily on exploit development capability, as this is where Claude Mythos Preview demonstrated a notable jump versus previous Claude models.
First, we ran the model on ExploitBench, which measures how well AI models can exploit known vulnerabilities in the V8 engine used by Google Chrome. Here we focus on the models’ ability to develop end-to-end exploits successfully, as this is the most relevant capability for attackers, and where we see significant changes between models. We find that GLM-5.3 develops end-to-end exploits in 50 of 410 attempts. Claude Mythos Preview did so at a similar rate—in 56 of 410 attempts.
In our internal Binary Exploitation benchmark,1 we test whether models can find and exploit vulnerabilities in popular open-source projects that participate in Google’s OSS-Fuzz project. Here, full credit is awarded for a full control-flow hijack. We evaluate several models on 100 tasks from the benchmark (selected at random), and find that GLM-5.3 develops full control-flow hijacks in 4% of the trials; Claude Mythos Preview did so in 6%. Although GLM-5.3 performs below Claude Mythos Preview here, a meaningful threshold has clearly been crossed: earlier models, like Claude Opus 4.6 and GLM-5.2, do not succeed in any of them.

Next, we evaluated how GLM-5.3 performs on open-ended offensive cyber tasks in the hands of human experts (mirroring our testing with Claude Mythos Preview earlier this year). Here, we select targets in which the human experts are unaware of existing vulnerabilities, then ask them to use the model to identify and exploit novel flaws. These experiments tested what the experts could do in a short time-frame: they typically ran for a day or less, with less than an hour of human focus in total.

In the first of these sessions, a researcher used GLM-5.3 on a sandboxed machine with a local Linux build of a popular web browser. Over the course of a day (and with limited human attention), GLM-5.3 found several previously unknown vulnerabilities in the browser’s JavaScript engine, and chained them together into a working exploit: a webpage that, when visited, reads arbitrary files from the visitor’s computer (shown in Figure 3). This exploit targets the Linux build of the browser, since that was the only environment made available to the model. However, we believe these vulnerabilities could also impact users on other platforms, though the path to exploitation there may be more complex. (We’ve disclosed these vulnerabilities to the maintainer.) Later in the session, the researcher also identified exploitable vulnerabilities in several other widely used systems with GLM-5.3, including wireless and graphics drivers and network-facing device software. We are currently reviewing these reports and we will disclose to maintainers as appropriate.
In a second session, a researcher used GLM-5.3-Flash (a smaller, less capable version of GLM-5.3) to develop an exploit for a known vulnerability (we’ve previously written about these “N-day” vulnerability exploits here). Here, the researcher focused on a recently disclosed flaw in Google Chrome (CVE-2026-11645) to see how quickly the model could turn a public fix into a working attack. The researcher provided GLM-5.3-Flash with public details of this CVE and another known flaw. With no significant direction from the researcher, GLM-5.3-Flash chained together exploits for these two flaws, building a reliable exploit chain for an ARM64 target, bypassing pointer-authentication (PAC) hardening. This took 20 minutes of human attention, plus eight hours of work for GLM-5.3-Flash. At Zhipu’s API prices, this effort would have cost $20.40.
GLM-5.3 lacks robust safeguards
GLM-5.3 has been released with some built-in safeguards: if a user asks for something clearly harmful, the model will often refuse.2 In our testing, we found that these safeguards could be bypassed or removed with a variety of simple techniques.
The most intensive—and most successful—method is a standard refusal reduction technique known as “abliteration.” Since GLM-5.3 is released as an open-weight model, users can reconfigure it to remove its refusals with little change in its capabilities. Several developers released abliterated versions of GLM-5.3 to the public within days of the model’s release.
To research how far abliteration allows attackers to bypass GLM-5.3’s safeguards, we produced an abliterated copy ourselves, and then ran it on three public benchmarks (JailbreakBench, HarmBench, and StrongREJECT) that measure how often a model complies with clearly harmful requests. Abliterating the model took our team—which had never previously attempted this task—about 2,200 GPU hours at a computation cost of roughly $4,400.3 Abliterating GLM-5.3-Flash took about 600 GPU hours. The edit took GLM-5.3’s refusal rate from above 90% to about 3% and 2% on the first two benchmarks (JailbreakBench and HarmBench) and to 12% on the third (StrongREJECT). Abliteration did not significantly reduce the model’s capabilities: on GPQA-Diamond, an evaluation that measures general scientific capabilities, the standard and abliterated models scored the same results; on a tested subset of the CyberGym evaluations, the abliterated version scored a few percent lower (as shown in the chart below).

In our testing, we observed that GLM-5.3’s safeguards can also be circumvented without using an abliterated version of the model. We placed the model in a simulated world4 in which it was given overtly malicious requests to attack critical systems. Out of the box, GLM-5.3 refused in all trials (as with the other models we tested). But we identified several simple ways to bypass the GLM models’ safeguards, such that it would respond to these requests in most or all cases. These include:
- Providing a deceptive prompt, such as telling the model that it is an autonomous red-team agent working on an exercise. This gets GLM-5.3 to engage 64% of the time.
- Prefilling the models’ thinking tokens so that it appears to have considered the user’s request and decided to proceed. This gets GLM-5.3 to engage 92% of the time.
- Using an abliterated version of the model, as described above. This gets GLM-5.3 to engage 100% of the time.
In our testing, none of these techniques got safeguarded Claude models to carry out the harmful tasks we tested. Claude’s safeguards blocked the requests that used deceptive prompts. The Anthropic API provides would-be attackers with no way to prefill Claude’s thinking. And since Claude’s weights are not provided to users, they cannot be abliterated to change Claude’s behavior.

To demonstrate how the abliterated version of GLM-5.3 is willing to engage in harmful tasks, we highlight one quote from the chain of thought that it generated:

What does this mean?
GLM-5.3 will likely give malicious actors access to capabilities that will allow them to find and exploit cyber vulnerabilities without meaningful restrictions. This is unlike any other similarly capable AI model, all of which were released with safeguards or through limited access programs. The release of GLM-5.3 is a meaningful step change in the cyber capabilities available to attackers. Anthropic and other US AI labs have published recent reports that disclose how cyber attackers have tried to use AI systems. Given this evidence, we think it’s likely both state and non-state actors will use models like GLM-5.3 to cause real-world harm.
On the other hand, models with this level of capability can also be used by defenders. Our view is that cyber defenders should use the best available tools that meet their needs. We're working to safely expand access to Claude's cyber capabilities to as many defenders as we can. Cyber defenders face attackers who will use every capable tool they can, and we believe defenders should be equipped with frontier models that are at least as good as those their adversaries are using.
Through Project Glasswing (and other efforts, like Patch the Planet), cyber defenders have made meaningful progress towards securing critical systems in advance of this moment—but much work remains to be done. While vetted defenders can now use even more advanced models like Claude Mythos 5.1 through our trusted access programs, a critical threshold in freely accessible capabilities has now been crossed. GLM-5.3 underscores the urgency of expanding access to advanced frontier models to a broader set of entities to empower cyber defenders.
Governments should conduct safety testing on sufficiently capable AI models, including successors to GLM-5.3. Without high-quality evaluations from independent sources, the impact of these capabilities might not become fully clear to model developers until it is too late. As AI developers across the world build increasingly capable open-weight models, we hope they work to appropriately safeguard these capabilities and prevent misuse.
