UnityTLS and Brotli decoder CVE

Two October 2026 bugs can reach Unity games: A compromised eMudhra certificate authority (CVE-2026-111943, UnityTLS CVE-2026-114406) and a Brotli decoder flaw (CVE-2026-111497). Read here what actions you have to take now.

By Tim UhlottFounder|Last updated: October 31, 2026|4 minutes read
cybersecurityunitycve
UnityTLS and Brotli decoder CVE
Two industry bugs can reach Unity games, some Unity services, Unity Pipeline Automation (UPA) apps, ML-Agents, and the experimental AI Assistant. The certificate failure is CVE-2026-111943, and UnityTLS tracks it as CVE-2026-114406. The decoder bug is CVE-2026-111497 in Google's Brotli library. Fixes for both are already shipping in Node.js, Python, Go, and major operating systems. Unity rates the risk inside its own ecosystem as low, and medium only in the worst case, with no evidence of impact on its users. CISA added the Brotli CVE to its known-exploited catalog on October 27 for other software, including Node.js.

What it means

On October 20, 2026, eMudhra revoked eight intermediate certificates whose private keys were weak enough to recover: six for websites, two for code signing. A holder can impersonate any site. UnityTLS borrows roots from the operating system, checks the chain itself, and cannot see revocation. A player on hostile Wi-Fi, or behind a compromised router, can have traffic read or changed while the device still trusts that chain. Analytics, tokens, and API keys are the realistic target, and players close it by updating the device. Windows, Xbox, and UWP need Microsoft's October 20 certificate update. WebGL is covered by the browser. Android games are covered by the October 2026 Play Services update. Mac, iPhone, and Linux need the bad root removed: Ubuntu with ca-certificates 20260816ubuntu0.X.1 or newer, SteamOS from 3.9. CVE-2026-111497, disclosed on October 21, is an out-of-bounds write in Brotli 1.0.3 through 1.2.0. A crafted stream can crash the game or run code in the game’s process when the build decompresses attacker-controlled data with BrotliStream, BrotliDecoder, or HttpClient Brotli decompression. This can affect your WebGL Brotli builds if you download data from an untrusted source. The Package Manager decompresses a registry response before it checks the signature. A malicious registry, or one impersonating a registry you trust, can crash the Editor on Windows and macOS and may run code in the Editor on Linux. Avoid scoped registries you do not control until the Editor is patched.

What you install

Unity's advisories, as of October 30, 2026:
ReleaseAffected versionsPatched release
Unity 6.3 LTS6000.3.0a1–6000.3.27f16000.3.27f2, available now
Unity 6.7 Beta6000.7.0a1–6000.7.0b66000.7.0b7, available now
Unity 6.0 LTS6000.0.0f1–6000.0.85f1Due next week
Unity 6.66000.6.0a1–6000.6.8f1Due next week
Unity 7.0 Alpha7000.0.0a7–7000.0.0a12Due next week
Install that release from Unity Hub or the Download Archive (opens in a new tab) before you publish. Update Unity 6.3 LTS and 6.7 Beta today. Unity 6.0 LTS, 6.6, and 7.0 Alpha updates arrive next week. Unity is still assessing 2022.3 and 2021.3. Search the project and plugins for the three Brotli APIs, and force a player update if those calls decompress data you do not control. Ask every player to install that update on their phone, PC, or console. ML-Agents affects only the training link between player and Editor. Unity will ship that package update next, plus a fix for the experimental AI Assistant, and will patch most services itself. Studios with UPA pipelines pinned to older app versions get separate guidance. Details are in the eMudhra advisory (opens in a new tab) and the Brotli advisory (opens in a new tab).
00 views
00 shares

Discussion about this post

Comments are reviewed before they appear on the article.

No comments yet. Be the first to start the discussion.

Frequently asked questions

Newsletter

Stay in the Loop.

Subscribe to our newsletter to receive the latest news, updates, and special offers directly in your inbox. Don't miss out!