Action required: upgrade to Flox 1.19.2 and reboot
Flox 1.19.1 and earlier ship a copy of Nix and Git that use a version of the Brotli decompression library with a critical vulnerability, CVE-2026-111497. Flox 1.19.2 links them against the fixed library. Upgrade to Flox 1.19.2 on every machine. After upgrading, our strong recommendation is to reboot each machine so all processes that may have been using the prior library are restarted.
Release 1.19.2 · flox/flox · GitHub
Flox 1.19.2 has an issue for users using the brew update method: Can't brew upgrade to 1.19.2 · Issue #4846 · flox/flox · GitHub that has now been addressed by Flox 1.19.3 Release v1.19.3 · flox/flox · GitHub.
What happened
On October 21, 2026, Google released Brotli 1.0.10, 1.1.1 and 1.2.1 to fix CVE-2026-111497, an out-of-bounds write in the Brotli decoder. Brotli versions 1.0.3 through 1.2.0 are affected. Google rates it 9.2 (Critical) under CVSS 4.0. A crafted Brotli stream can corrupt memory in the process decoding it, which can lead to remote code execution.
The flaw is in the Brotli library, not in Nix or Flox. But the Nix and Git that Flox installs are linked against Brotli 1.2.0, so they inherit it. Nix decodes Brotli in two places:
- HTTP client asks servers for Brotli-compressed responses and decompresses them.
- Decompresses Brotli-compressed packages and build logs from binary caches.
Git reaches the same library through curl.
We are not aware of an exploit against Flox, and we have seen no reports of this vulnerability being exploited in the wild.
Are you affected
You are affected if you run Flox 1.19.1 or earlier on Linux or macOS.
An attacker needs to get a malicious Brotli stream in front of Nix or Git. That means one of:
- A compromised binary cache (substituter), or the CDN in front of it
- A compromised or spoofed server that hosts a flake Nix downloads
- A compromised or spoofed server that hosts source code for packages built from source
- An attacker on your network who can impersonate a server despite HTTPS
The default binary caches use HTTPS, which raises the bar considerably. But Nix fetches from many more hosts than its caches, and any of them can return a Brotli response. A configuration change cannot close this. The fix is to run Nix linked against a patched Brotli.
What changes in Flox 1.19.2
- Nix and Git use Brotli 1.2.1. The Nix and Git that Flox installs, and the curl they use, are rebuilt against Brotli 1.2.1, which contains the fix. Nothing else changes.
- Existing environments are fixed without changes. You do not need to edit, upgrade, re-lock or pull anything.
- It includes the certificate authority fix from Flox 1.19.1. If you are upgrading from 1.19.0 or earlier, see the 1.19.1 security notice as well.
What you need to do
-
Upgrade Flox to 1.19.2 on every machine, including CI runners and build agents. Installers and packages are linked from the 1.19.2 release on GitHub.
-
Reboot after upgrading. The Nix daemon keeps the old Brotli library loaded until it restarts. This matters most on Debian and Ubuntu, where upgrading the
.debpackage does not restart the daemon. If you cannot reboot, restart the Nix daemon. On macOS runsudo launchctl kickstart -k system/org.nixos.nix-daemon, and on Linux runsudo systemctl daemon-reload && sudo systemctl restart nix-daemon. -
Confirm the upgrade.
flox --versionshould print1.19.2. On Linux, this command shows which Brotli the running Nix daemon has loaded, and should print a path containingbrotli-1.2.1:sudo grep -o '/nix/store/[^ ]*brotli[^ ]*' /proc/$(pgrep -x nix-daemon)/maps | sort -u
You do not need to rebuild or republish packages made with flox build or flox publish.
What Flox 1.19.2 does not cover
Flox 1.19.2 fixes the Nix and Git that Flox itself runs. It does not change the packages inside your environments.
- Packages from the Flox catalog. Packages that link Brotli, including
nodejs,curl,git,freetype,brotliand Python’sbrotlicffi, are built from nixpkgs. As of October 27, the nixpkgs fix has not yet reached the branches the Flox catalog is built from. These packages will pick up the fix once it does.flox listorflox upgrade --dry-runwill show you when package upgrades are available.flox upgradethe environments that have upgrades available. - Container images made with
flox containerize. An image contains the packages in your environment, so it carries whatever Brotli those packages use. Rebuild images once the catalog packages they contain are fixed. - Tools outside Flox. Node.js, Python’s
Brotlipackage, curl, Git for Windows and other software installed outside Flox ship their own copy of Brotli. Update them through their own channels.
If you cannot upgrade yet
There is no setting that stops Nix decoding Brotli. Until you can upgrade:
- Use only HTTPS binary caches you trust, and avoid adding new substituters.
- Avoid running Flox or Nix on networks you don’t control, such as public Wi-Fi.
- Prefer building in CI on networks you control.
FloxHub
FloxHub’s servers were also affected. Fixes were deployed to production on October 27, and no action is needed from FloxHub users.
Questions
If you have questions about this notice, or need help confirming that a specific environment, image or pipeline is clear, contact Flox support.