CVE-2026-15226
HighCVSS 8.4Exploitation Probability (EPSS)
Low risk3th percentile - higher than 3% of all known CVEs
Summary
Vulnerability in snapd (Canonical) in the snap-confine component. Default seccomp templates do not block operations creating files with setuid flags, allowing applications in strict snap sandboxes to create and execute setuid binaries, bypassing security restrictions. Fixed by hardening the seccomp template engine.
Risk Assessment
Risk involves potential privilege escalation within the snap container, leading to isolation breach and unauthorized actions.
Recommendation
Update snapd to the latest patched version and monitor snap environments for suspicious activity.
Other vulnerabilities in snapd
Original NVD description (English source)
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.