Ubuntu snap-confine Flaw Could Give Local Users Root on Default Desktop Installs

Cybersecurity researchers have disclosed details of a new local privilege escalation (LPE) vulnerability in snap-confine that an unprivileged user can trigger to obtain root access and gain complete control of a target environment.

The high-severity flaw, tracked as CVE-2026-8933 (CVSS score: 7.8), impacts default installations of Ubuntu Desktop 24.04, 25.10, and 26.04. The disclosure comes as 442 security flaws in Linux have been publicized over the past three days.

“The issue stems from a security hardening change that inadvertently introduced a race condition during sandbox initialization,” Saeed Abbasi, head of Threat Research Unit (TRU) and director of product at Qualys, said.

Snap-confine is a program used internally by snapd to construct the execution environment for snap applications. Snapd is the background service or daemon that manages snap packages on Linux systems. Snaps are nothing but a software packaging format devised by Canonical that allows an application to run securely in an isolated sandbox across most Linux distributions.

“Snapd runs a sub-process called snap-confine, which is responsible for creating the necessary confinement for the snap,” according to Canonical.

Although recent Ubuntu releases make use of the set-capabilities model to enforce the principle of least privilege (PoLP) as a way to minimize the attack surface, the changes allow snap-confine to be executed with the effective UID of the calling user, at the same time still retaining near-root capabilities.

“During sandbox setup, the binary creates temporary directories and files under /tmp that are initially owned by the unprivileged user,” Qualys explained. “Ownership is transferred to the root shortly after, but a narrow window remains during which the caller retains full control.”

The problem identified by the cybersecurity vendor is the result of two concurrent race conditions –

• An attacker mounts a malicious FUSE file system over the temporary scratch directory immediately after creation, bypassing the mount namespace isolation applied by snap-confine and keeping the directory accessible outside the sandbox.
• The attacker creates a symbolic link (aka symlink) pointing to an arbitrary target file, effectively redirecting file operations to sensitive system locations.

By manipulating file permissions before the system transfers ownership, the attacker can inject malicious rules into system directories and gain root code execution, Qualys noted.

“When snap-confine attempts to create a sandbox file, the open() call follows the symlink and writes to the target,” Abbasi said. “A second race condition allows the attacker to widen file permissions to 0666 before snap-confine calls fchown() to transfer ownership to root.”

“To bypass AppArmor confinement, the exploit targets the /run/udev/** path, which permits read-write access. By dropping a malicious .rules file in /run/udev/rules.d/ and triggering a FUSE mount/unmount cycle, the attacker forces systemd-udevd to execute arbitrary commands as root.”

To counter the risk posed by CVE-2026-8933, organizations must apply the latest snapd updates as soon as possible.