Skip to main content

snapd CVE-2026-15226

| EUVDEUVD-2026-46261 HIGH
Execution with Unnecessary Privileges (CWE-250)
2026-07-21 canonical GHSA-9pj8-7m3m-mh5h
8.4
CVSS 3.1 · Vendor: canonical
Share

Severity by source

Vendor (canonical) PRIMARY
8.4 HIGH
AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
vuln.today AI
8.4 HIGH

Attacker needs local code execution inside a confined snap (AV:L/PR:L), the bypass is straightforward (AC:L), and escaping confinement crosses a trust boundary (S:C) with high confidentiality/integrity impact and no availability effect.

3.1 AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N

Primary rating from Vendor (canonical).

CVSS VectorVendor: canonical

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

2
Analysis Generated
Jul 21, 2026 - 15:00 vuln.today
CVE Published
Jul 21, 2026 - 14:02 cve.org
HIGH 8.4

DescriptionCVE.org

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.

AnalysisAI

Sandbox confinement bypass in Canonical snapd (snap-confine) affects all supported Ubuntu LTS releases (16.04 through 26.04) because the default seccomp templates fail to block system calls that create or set set-user-ID flags on files. A process already running inside a strictly confined snap can compile or drop a binary, mark it setuid, and then execute it to escape confinement assumptions and perform privileged actions within the container namespace. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Gain code execution inside confined snap
Delivery
Write attacker binary to snap-writable path
Exploit
Set setuid bit via unfiltered syscall
Execution
Execute setuid binary
Impact
Escape confinement / run privileged actions in namespace

Vulnerability AssessmentAI

Exploitation Exploitation requires the attacker to already have arbitrary code execution as the confined process inside a strictly confined snap sandbox (PR:L, AV:L) - this is a local, post-compromise escalation, not a remote entry point. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N) describes a local attacker who already controls a low-privileged process inside a confined snap, with low complexity, no user interaction, and a scope change reflecting escape from the sandbox boundary into the host namespace. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario An attacker who has compromised an application running inside a strictly confined snap (for example via a bug in the snap's own code) writes a small binary into a writable path, uses the un-filtered syscall to set its setuid bit, and executes it. Because the seccomp template did not block that operation, the setuid binary runs with elevated ownership and lets the attacker drop confinement restrictions or perform privileged actions inside the namespace. …
Remediation Patch available per vendor advisory: Canonical has resolved the issue by hardening the seccomp template engine to block creation and execution of setuid executables by sandboxed snap processes - apply the updated snapd package for your release via the standard channel (e.g. … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours: Identify and inventory all snap packages installed across Ubuntu LTS systems (16.04, 18.04, 20.04, 22.04, 24.04, 26.04) and classify by trust level and network exposure. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

CVE-2026-15226 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy