CVE-2026-15226
snapd sandbox bypass allows confined snaps to create/execute setuid binaries.
Is CVE-2026-15226 being exploited?
Not confirmed. CVE-2026-15226 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.15% probability of exploitation in the next 30 days.
How severe is CVE-2026-15226?
CVE-2026-15226 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-15226?
Yes. A fix has been recorded for CVE-2026-15226. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-15226 affect?
CVE-2026-15226 affects Canonical snapd (snap-confine), Ubuntu and Linux systems with snapd installed, Devices using snaps for app delivery. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-15226?
Update snapd to the patched release; restrict/uninstall untrusted snaps until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
A confined snap can create and run setuid binaries to bypass sandboxing and perform privilege escalation or execute privileged actions.
Immediate action required