CVE-2026-3888 in Ubuntu 24.04: snapd Vulnerability Enables Local Privilege Escalation

CyberSecureFox 🦊

A new high-severity vulnerability, CVE-2026-3888, has been identified in Ubuntu Desktop 24.04 and newer, allowing a local, unprivileged attacker to escalate privileges to root. With a CVSS score of 7.8, the flaw impacts systems using default settings and is linked to how Ubuntu handles temporary directories and the isolation of snap applications.

Overview of CVE-2026-3888 in Ubuntu 24.04 and Newer

The issue was discovered by the Qualys Threat Research Unit and stems from unsafe interaction between two standard Ubuntu components: snap-confine (part of snapd, responsible for building the sandbox for snap packages) and systemd-tmpfiles (the service managing cleanup of temporary directories such as /tmp, /run and /var/tmp).

Under normal conditions, systemd-tmpfiles periodically removes old files and directories from /tmp to prevent disk clutter. In this case, however, the automated cleanup creates a window of opportunity for a local privilege escalation attack if a user can precisely time actions between cleanup cycles.

Technical Details: snap-confine, systemd-tmpfiles and /tmp/.snap

The core of CVE-2026-3888 is the directory /tmp/.snap, which snap-confine uses while preparing the sandboxed environment for snap applications. By default, systemd-tmpfiles periodically deletes /tmp/.snap as “expired”: typically after about 30 days on Ubuntu 24.04 and roughly 10 days on more recent builds.

The exploitation scenario works as follows: during a regular cleanup cycle, systemd-tmpfiles removes the legitimate /tmp/.snap directory. After that, an unprivileged local user can recreate the same path with attacker-controlled content. On the next launch of any snap application, snap-confine performs bind mounts of this directory as root, effectively granting the attacker the ability to run arbitrary code in a highly privileged context.

According to the research, the attacker needs only basic local access (for example, a regular user account or a compromised low-privilege service). No user interaction is required—no clicks, prompts or confirmations. Although exploitation depends on the time elapsed since installation or the last cleanup (around 10–30 days), the potential impact is a full compromise of the affected Ubuntu system.

Affected Ubuntu Versions and snapd Security Updates

The vulnerability is confirmed on default Ubuntu Desktop installations of current supported branches. Canonical has already released patches for snapd, and administrators should verify that the following minimum versions are installed:

  • Ubuntu 24.04 LTSsnapd 2.73+ubuntu24.04.1 or newer;
  • Ubuntu 25.10 LTSsnapd 2.73+ubuntu25.10.1 or newer;
  • Ubuntu 26.04 LTS Devsnapd 2.74.1+ubuntu26.04.1 or newer;
  • Upstream snapd — fixed starting from snapd 2.75.

Users and administrators should apply updates via apt, the graphical “Software & Updates” tools, or built-in automatic update mechanisms. In the context of modern cyber threats, timely patch management remains one of the most effective controls for reducing exposure to local and remote exploitation.

Related Issue: Race Condition in uutils coreutils

In parallel with CVE-2026-3888, Qualys reported a separate vulnerability involving a race condition in the Rust-based uutils coreutils project, an alternative implementation of GNU coreutils.

The flaw allows an unprivileged local user to replace directory entries with symbolic links at the moment when scheduled tasks (such as cron jobs running as root) invoke these utilities. Successful exploitation could lead to the deletion of arbitrary files or the creation of conditions that facilitate further privilege escalation or data destruction.

To mitigate the risk in Ubuntu 25.10, the distribution switched the default rm command back to the GNU coreutils implementation instead of the uutils version. The upstream uutils coreutils repository has already incorporated fixes, and users are advised to track security updates provided by their specific Linux distributions.

Hardening Ubuntu and Linux Systems Against Similar Vulnerabilities

These incidents highlight a critical reality of Linux security: even mature, widely deployed components such as systemd, snapd and coreutils can introduce serious vulnerabilities when complex subsystems interact in unexpected ways. Temporary file handling, sandboxing logic and scheduled maintenance tasks are common attack surfaces in local privilege escalation scenarios.

To reduce the risk of exploitation of CVE-2026-3888 and similar flaws in Ubuntu and other Linux distributions, organizations should:

  • Enable automatic security updates (for example, via unattended-upgrades) on desktops and servers where appropriate.
  • Regularly patch core components such as snapd, systemd and coreutils, prioritizing updates that address privilege escalation and sandbox escapes.
  • Limit the number of local users with interactive shell or GUI access, especially on sensitive systems and shared workstations.
  • Monitor vulnerability disclosures via CVE feeds, vendor security advisories and distribution mailing lists to react quickly to high-impact issues.
  • Audit and minimize root cron jobs, ensuring they use trusted utilities and are not exposed to writable directories or user-controlled paths.

Strengthening update processes, monitoring vulnerability intelligence and regularly reviewing system configurations significantly lowers the chance that a local flaw such as CVE-2026-3888 or the uutils coreutils race condition will be successfully exploited. Organizations that treat patching and configuration management as continuous security practices, rather than one-time tasks, are better positioned to keep their Ubuntu and broader Linux infrastructure resilient against evolving threats.

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.