Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-8933: Local Privilege Escalation in snap-confine Set-Capabilities Configuration

Published Jul 21, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS0.31%24th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-8933CWE-362

CVE-2026-8933 is a high-severity local privilege-escalation vulnerability in snap-confine, the snapd helper that constructs execution sandboxes for Snap applications. It affects snap-confine deployments using file capabilities rather than the conventional setuid-root configuration. During sandbox initialization, snap-confine creates temporary resources while executing with the invoking user's effective UID but retaining powerful Linux capabilities. Race windows before ownership changes permit an attacker to manipulate those resources. Privileged file creation follows attacker-controlled symbolic links because the relevant open operation lacks no-follow protection, while a separate race permits permissions to be widened before ownership is transferred. An attacker can combine these conditions with a FUSE mount to retain access across namespace setup and create a privileged udev rule that systemd-udevd executes as root. Setuid-root snap-confine installations are not affected.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A local unprivileged attacker can bypass snap-confine sandbox and privilege boundaries, create or modify attacker-selected files within the constraints of the snap-confine AppArmor policy, and cause execution of arbitrary commands with full root privileges. Successful exploitation results in complete compromise of the affected host, including the ability to alter system configuration, establish persistence, access protected data, and disable security controls.

Mitigation

If you can’t patch tonight, do this now.

Promptly restrict local interactive and shell access to trusted users until patched packages are deployed. Prioritize shared workstations, developer endpoints, and systems on which untrusted code can execute locally. No reliable temporary configuration-only mitigation is specified for affected set-capabilities deployments; applying the vendor update is the required corrective action.

Remediation

Patch, then assume compromise.

Install Canonical's patched snapd packages and reboot the system. Fixed versions are snapd 2.76+ubuntu22.04.1 or later for Ubuntu 22.04 LTS, 2.76+ubuntu24.04.1 or later for Ubuntu 24.04 LTS, and 2.76+ubuntu26.04.3 or later for Ubuntu 26.04 LTS. Upstream snapd version 2.76.1 contains the fix. Verify the installed package version rather than relying on the operating-system release or prior patch state.

Public exploits

Exploits

2 exploits validated by Mallory's analysis.

View more in app →
CVE-2026-8933Standalone Linux local privilege-escalation repository with 23 files: three C files, nine Bash scripts, one Python script, a README, three JSON artifacts, three patches and three advisory/discussion captures. t18.c is the main exploit, _t18poc.sh builds and orchestrates it, _ftrig.c implements a minimal FUSE filesystem to trigger udev processing, and _rootshell.py provides PTY-based access through the planted account. _msc_273.c is a bundled snapd 2.73 source reference rather than a separate exploit. Other scripts cover repeated runs, diagnostics, payload capability tests, shell regression tests, cleanup and state/build checks. The exploit targets capability-enabled snap-confine, which retains the invoking user's effective UID while holding powerful capabilities. Scratch directories and newly created files can therefore briefly belong to the attacker before being chowned to root. The documented chain monitors scratch-directory creation, uses a controlled systemd user scope and cgroup freezing to coordinate namespace races, substitutes symlinks, and redirects a regular-file replication open lacking O_NOFOLLOW into the host udev rule directory. A concurrent spinner changes permissions during the ownership window and repeatedly writes the rule, counteracting later truncation. A FUSE mount event then causes systemd-udevd to execute the rule's shell payload as root. The default payload creates a known-password UID-0 account rather than relying on setuid binaries, which the bundled probe says are restricted by udev's RestrictSUIDSGID setting. This is substantive exploit code, not merely detection or a README, and no clear fake-exploit behavior is apparent. Recursive deletion is scoped to cleanup artifacts, although its broad temporary-directory globs and privileged account edits still carry operational risk. Payload commands and paths are configurable, but this is not part of an identified exploitation framework. The README's success and reliability claims were not independently verified, and important portions of the main C file and driver are truncated in the supplied material. Version and remediation evidence is inconsistent: bundled CVE metadata gives an affected range of 2.75.0 through versions before 2.76.1, while the README claims success on 2.76.3 and references 2.73 source. The supplied patches mainly address /tmp/snap-private-tmp handling or release metadata; they do not visibly implement the advertised sc_replicate_base_rootfs O_NOFOLLOW change. The API JSON artifact is a rate-limit error, not a fix. These discrepancies prevent a definitive affected-version or remediation conclusion from this repository alone. No outbound networking, command-and-control, exfiltration or runtime download behavior is visible. Advisory URLs and the IP address in the saved API error are reference artifacts, not exploit destinations. Repository URL, git reference and archive size were not provided; empty strings and zero denote unavailable metadata.songzzzz · Disclosed Oct 17, 2026 · c · bash · localOperationalCVE-2026-8933This standalone repository presents a local privilege-escalation exploit attributed to CVE-2026-8933. Its 11 files comprise poc.c, a Makefile, two Markdown documents, six C headers, and one header-template file containing only '404: Not Found'. The seven C source/header files account for the reported code-file count; shell payloads are generated by the exploit rather than supplied as separate scripts. The vulnerability combines attacker ownership of temporary objects in file-capabilities snap-confine with a rootfs replication open(O_CREAT|O_TRUNC) lacking O_NOFOLLOW. The documented implementation creates a user-owned, snap-named systemd scope, uses debug output and cgroup freezing to intercept namespace construction, redirects scratch-directory resolution between .dA and .dB, and turns replicated regular-file paths into symlinks targeting /run/udev/rules.d. Freezer-controlled execution and chmod spinner processes attempt to preserve write access across the subsequent fchown. A FUSE-generated bdi add event then causes systemd-udevd to execute the injected PROGRAM as root. The default payload records id output in /tmp/pwned. Features include configurable snap/application selection, regular-file filtering, retries, timing controls, custom payload commands, diagnostics, and cleanup. Cleanup reportedly uses a transient system service because udev's own namespace and syscall restrictions prevent direct mount cleanup. Failed or interrupted attempts can leave mounts, directories, or root-owned rule files. No network exploitation, exfiltration, or callback behavior is shown. Important limitations: most of poc.c and some headers are truncated in the supplied content, so full implementation verification was not possible. The introductory C comment describes an older FUSE-overmount/detach approach that the README and NOTES explicitly say was abandoned; visible .dA/.dB globals support the newer symlink-switch design. Claimed successful tests, the CVE attribution, and the stated fix in snapd 2.77.1 are repository assertions, not independently verified findings. No repository URL, git reference, or archive size was supplied; empty metadata strings and size 0 indicate unavailable values.yifengchen-cc · Disclosed Oct 23, 2026 · c · makefile · localOperational
FAQ

Frequently asked questions

Is CVE-2026-8933 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-8933 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-8933?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2026-8933, the earliest disclosed Oct 17, 2026.
Is there a patch for CVE-2026-8933?
Install Canonical's patched snapd packages and reboot the system. Fixed versions are snapd 2.76+ubuntu22.04.1 or later for Ubuntu 22.04 LTS, 2.76+ubuntu24.04.1 or later for Ubuntu 24.04 LTS, and 2.76+ubuntu26.04.3 or later for Ubuntu 26.04 LTS.
How severe is CVE-2026-8933?
CVE-2026-8933 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.31% (24th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

87 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+9 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity74Community discussion across Reddit, Mastodon, and other social sources.