Skip to main content
Mallory
HighVulnerability

CVE-2026-15226: Sandbox Confinement Bypass in Canonical snapd snap-confine via Missing setuid Restriction

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.
CVSS8.4High · v3.1
EPSS0.18%8th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-15226CWE-250 · Execution with Unnecessary…

CVE-2026-15226 is a high-severity sandbox confinement bypass in Canonical snapd affecting snap-confine and its seccomp template generation logic. The flaw stems from default seccomp security templates that failed to filter or reject operations involved in creating or manipulating executables with the set-user-ID attribute. As a result, a process running inside a strictly confined snap could compile or place binaries and mark them setuid. If those binaries are then executed, the process can violate snap confinement assumptions and bypass intended sandbox restrictions. The issue was fixed by hardening the seccomp template engine to block the creation and execution of setuid executables by sandboxed snap processes.

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.

Successful exploitation allows a local attacker with code execution inside a strictly confined snap to bypass snap sandbox restrictions and transition from confined execution to more privileged execution. Reported outcomes include escape from Snap confinement from confined root to unconfined root, execution of privileged actions inside the container namespace that should have been blocked, and compromise of confidentiality and integrity boundaries enforced by snap confinement.

Mitigation

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

No complete workaround is documented. Until patched, reduce exposure by limiting execution of untrusted or potentially malicious strictly confined snaps, restricting local attacker access to systems running vulnerable snapd versions, and monitoring snap environments for unexpected creation or execution of setuid binaries. The effective long-term mitigation is vendor patching.

Remediation

Patch, then assume compromise.

Upgrade snapd to a fixed release that hardens seccomp template generation against creation and execution of setuid executables by sandboxed processes. Upstream versions earlier than 2.76.1 are affected. Fixed Ubuntu package versions include 2.76+ubuntu26.04.3 for Ubuntu 26.04 LTS, 2.76+ubuntu24.04.1 for Ubuntu 24.04 LTS, 2.76+ubuntu22.04.1 for Ubuntu 22.04 LTS, 2.67.1+20.04ubuntu1~esm3 for Ubuntu 20.04 LTS, 2.61.4ubuntu0.18.04.1+esm4 for Ubuntu 18.04 LTS, and 2.61.4ubuntu0.16.04.1+esm4 for Ubuntu 16.04 LTS. Reboot after applying updates where required to complete the change.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-15226 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-15226 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-15226?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-15226.
Is there a patch for CVE-2026-15226?
Upgrade snapd to a fixed release that hardens seccomp template generation against creation and execution of setuid executables by sandboxed processes. Upstream versions earlier than 2.76.1 are affected.
How severe is CVE-2026-15226?
CVE-2026-15226 has a CVSS v3.1 score of 8.4 (High) and an EPSS score of 0.18% (8th percentile) as of Sep 25, 2026.
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 activity2Community discussion across Reddit, Mastodon, and other social sources.