GLM-5.3 Officially Released: Post-Training Scaling, Emergent Cyber, Weights in 2 Weeks

Verified status at a glance

Rollout order this time was blog + Coding Plan first, changelogs trailing — the mirror image of a docs-first rollout. If your signal is "is it in the changelog yet", you'll be late.

The numbers (vendor-reported, from the official table)

All scores below are Z.ai's own reported numbers from the announcement. Selected rows; the full table in the blog covers ~20 benchmarks.

• Honest read of the table: GLM-5.3 roughly matches or beats Kimi K3 and DeepSeek-V4-Pro-0813 (62.7 DeepSWE) across coding/agentic rows, sits at or near Opus 4.8, and still trails Claude Fable 5 and GPT-5.6 Sol on the hardest rows (Terminal Bench 3.0, DeepSWE, ExploitBench). Z.ai itself says the gap to the closed frontier is widest exactly where it improved most.
• Token efficiency: on the in-house Z.ai Code Bench, at High effort 5.3 hits 31.4% with ~50K output tokens, surpassing Opus 4.8's 29.5% at 120K; Fable 5 still leads at 39.5% (Max effort).
• Vendor claims, labeled as such: "most capable open-weights model for coding", open-source SOTA on Terminal Bench 3.0 and ALE, ~50% coding-experience improvement. Independent verification arrives with the weights in ~2 weeks.

The cyber story is real-world, not just benchmarks

The most unusual part of the release: Z.ai ran GLM-5.2/5.3 against real codebases with several security teams in China. After expert review and deduplication, the model identified 2,436 vulnerabilities across 269 projects, including 1,097 medium-to-high severity issues — spanning kernels, browser engines, open-source infrastructure, web apps, and network protocols. The oldest flaw dates to 1981; on average a vulnerability had lived 26.6 years before discovery.

• Findings flow into a public Z.ai Security Disclosure Ledger — per unite.ai's coverage, 53 were public with CVEs at announcement and 2,383 remain under embargo (Linux kernel use-after-free, WebKit/Safari memory bugs, FreeBSD parameter validation among them).
• On exploitation-depth benchmarks the pattern is consistent: big jumps from 5.2 (ExploitGym 29→105 tasks @2h), but Mythos 5 and GPT-5.6 Sol remain well ahead. This is a strong defensive/security-review capability, not an offense frontier.
• Z.ai's own framing: capability "developed faster than we expected" as post-training scaled — hence the two-week safety hardening window before weights ship.

API builders: one breaking change to plan for

• Migration required: GLM-5.3 supports thinking effort low / high / max (default max, recommended for coding) — and thinking.type: "disabled" is no longer supported. The official docs are blunt: change it to enabled and set reasoning_effort before switching the model ID, "otherwise, the request will fail."
• Coding Plan economics: the plan is now points-based (input, cached input, and output counted separately); weekdays 14:00–18:00 UTC+8 are peak, everything else — including weekends — consumes 50% of standard points. ZCode adds a 98%+ cache hit rate and a 1.5x quota boost through Aug 31.
• Through relays like ChinaModelAPI: production stays on glm-5.2 for now; we'll add the 5.3 model ID once the upstream API is generally available and healthy. When you migrate, budget for the mandatory thinking-parameter change above.
• Same base, same envelope: 1M context / 128K output / same capability surface (thinking, streaming, function calling, context cache, structured output, MCP) — so migration is a model-ID + params swap plus regression runs on your agent loops.
• Still text-only: vision was the top community ask in Zhipu's feedback round; it didn't make this release.

Overseas reaction

• Reddit r/LocalLLaMA has a "GLM 5.3 Released" thread linking the official blog, with the headline detail that weights land "in two weeks".
• Reddit r/ZaiGLM users on Lite plans reported GLM-5.2 "responding very differently" in the days before announcement — consistent with a staged rollout behind the 5.2 label rather than a big-bang switch.
• unite.ai covered the launch under "a cyber capability that outgrew its training", highlighting the 2,436-vulnerability disclosure program and the end-of-August weights window for independent verification.
• Laurie Voss (LinkedIn) — a widely read commentator on open-weight models — framed 5.2-as-go-to with "GLM 5.3 open weights in development", putting the GLM line ~6–9 months ahead of the open-weight pack in his telling.
• X/Twitter tech commentators (e.g. Julian Goldie) had tracked the pre-release leaks; the official @zai_org announcement settles the "when" question.

Primary sources

• Z.ai official blog — GLM-5.3: Frontier Coding with Emergent Cyber Capabilities (announcement, full benchmark table, API changes, weights timeline)
• Zhipu official docs — GLM-5.3 model page (specs; Coding Plan rollout)
• unite.ai — Z.ai Launches GLM-5.3 (third-party coverage incl. disclosure ledger details)
• Reddit r/LocalLLaMA — GLM 5.3 Released thread
• Reddit r/ZaiGLM — rollout-behind-5.2-label observations
• Z.ai Security Disclosure Ledger

FAQ