CVE-2026-15226: snapd snap-confine Sandbox Confinement Bypass via Omission of setuid Restriction in Seccomp Templates
A sandbox confinement bypass vulnerability exists in Canonical snapd within its internal execution environment compiler (snap-confine). The default seccomp security templates generated by the engine to restrict system calls do not filter or reject process operations capable of creating or manipulating file execution flags with set-user-ID attributes. Consequently, an application running within a strictly confined snap environment can successfully compile or drop binaries and apply setuid properties to them. If a compromised or malicious process inside the snap sandbox executes these generated setuid binaries, it can potentially circumvent architectural sandboxing assumptions, drop intended restriction policies, or execute privileged actions inside the container namespace that should otherwise be strictly blocked. The vulnerability has been resolved by hardening the seccomp template engine to block the execution and creation of setuid executables by sandboxed snap processes.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-15226?
The severity of CVE-2026-15226 is classified as high with a score of 8.4.
How do I fix CVE-2026-15226?
To fix CVE-2026-15226, update to the latest version of snapd that addresses the sandbox confinement bypass issue.
What systems are affected by CVE-2026-15226?
CVE-2026-15226 affects the Canonical snapd snap-confine software.
What type of vulnerability is CVE-2026-15226?
CVE-2026-15226 is a sandbox confinement bypass vulnerability due to insufficient seccomp restrictions.
How can CVE-2026-15226 impact my system's security?
CVE-2026-15226 can allow unauthorized access and manipulation of processes, compromising the security of your system.