CVE-2026-110451: Nix Seatbelt sandbox escape on macOS

CVE-2026-110451 · Severity: medium · CVSS 4.3 · Published 2026-10-14

Nix and Lix are package managers used to build and deploy software reproducibly on Linux and macOS. A flaw in macOS sandbox configuration allows builds to escape confinement and run with elevated privileges when certain size thresholds are crossed. This could enable an attacker to gain unauthorized system access or bypass security controls on affected macOS systems where sandboxing is enabled.

Technologies: Lix, Nixos Nix. Vendors: Lix, Nixos.

Quick answers

Is CVE-2026-110451 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-110451 being exploited in the wild.
How severe is CVE-2026-110451?
Medium severity, with a CVSS score of 4.3, published 14 October 2026.
Which products and versions are affected?
Lix before 2.94.3, 2.95.4, 2.96.0; Nixos Nix before 2.28.8, 2.30.6, 2.31.6, 2.34.9, 2.35.3.
Is there a fix for CVE-2026-110451?
Yes: fixed in Nix 2.35.3, 2.34.9, 2.31.6, 2.30.6, 2.28.8; Lix 2.94.3, 2.95.4, 2.96.0. Until then: This issue affects macOS only when sandbox = true or sandbox = relaxed is configured; the default sandbox = false is not affected. Users who have not explicitly enabled sandboxing are protected by default.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-10-14"},{"kind":"advisory","at":"2026-10-13"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-110451 attacked?
It is attacked with local access, in a software library.
Am I affected by CVE-2026-110451?
Check whether you run Lix or Nixos Nix at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: Nix 2.35.3, 2.34.9, 2.31.6, 2.30.6, 2.28.8; Lix 2.94.3, 2.95.4, 2.96.0

This issue affects macOS only when sandbox = true or sandbox = relaxed is configured; the default sandbox = false is not affected. Users who have not explicitly enabled sandboxing are protected by default.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-10-14"},{"kind":"advisory","at":"2026-10-13"}]

Technical details

A missing optional path in the Seatbelt sandbox profile can cause an unqualified (allow …) directive to be generated when the profile crosses an internal size threshold, leaving the build unconfined. This affects only macOS systems with sandbox = true or sandbox = relaxed configured; the default is sandbox = false. The vulnerability allows deliberate escape from the build sandbox and privilege escalation in multi-user daemon installations.

Affected products

  • NixOS Nix before 2.28.8, 2.30.6, 2.31.6, 2.34.9, 2.35.3
  • Lix Lix before 2.94.3, 2.95.4, 2.96.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.