CVE-2026-15226Patch

LOWCVSS 8.4 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch affected systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

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.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-250

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

STABLE

Threat summary

  • Patch or workaround signal is available
  • 3 mentions across 3 observed days
  • Momentum state: stable

What's happening

  • Patch or workaround mentioned in 2 signals
  • Technical details provided in 3 signals
  • Disclosure: 1 classified signal
  • Peaked 2d ago at 1 mentions (2026-07-21); latest day: 1
  • 3 total mentions across 3 days

Deep dive

Activity timeline3 mentions / 3d
00111Mentions · 2026-07-21: 1Mentions · 2026-07-22: 1Mentions · 2026-07-23: 1Patch / Workaround · 2026-07-21: 1Patch / Workaround · 2026-07-22: 1Technical Details · 2026-07-21: 1Technical Details · 2026-07-22: 1Technical Details · 2026-07-23: 107-2107-2207-23
Signal classification2 categories
Patch
266.7%
Disclosure
133.3%
Referenced assets2 URLs
Classification over time
DateTotalLabels
2026-07-211
Patch1
2026-07-221
Patch1
2026-07-231
Disclosure1
Full discourse3 posts
  • Open Source Security mailing list@oss_security
    Patch

    snapd: 3 CVE fixes being released https://www.openwall.com/lists/oss-security/2026/07/21/1 CVE-2026-8933: LPE in set-capabilities versions of snap-confine (found by @Qualys) https://www.openwall.com/lists/oss-security/2026/07/21/2 CVE-2024-5300: Unauthorized Access to Hashed Passwords CVE-2026-15226: Omission of setuid Restriction

    Post summary

    The message announces that patches for three CVEs have been released, providing brief vulnerability details but no exploit code or evidence of active exploitation.

    02060856
    4.7K followersView on X
  • Diario฿itcoin@DiarioBitcoin
    Disclosure

    🔒💥 ¡ALERTA DE SEGURIDAD EN UBUNTU! Canonical revela 3 vulnerabilidades críticas en snapd que afectan versiones desde Ubuntu 16.04 LTS. CVE-2026-8933 permite escalado de privilegios. CVE-2026-15226 posibilita escape de confinación. CVE-2024-5300 expone contraseñas hasheadas. La seguridad de tus aplicaciones podría estar en riesgo. Es crucial evaluar las instalaciones y tomar medidas.

    Post summary

    Canonical has announced three critical snapd vulnerabilities (CVE‑2026‑8933, CVE‑2026‑15226, CVE‑2024‑5300) affecting Ubuntu 16.04 LTS and newer, involving privilege escalation, confinement escape, and hashed password exposure.

    100101.0K
    213.0K followersView on X
  • Upwind Security MDR@UpwindMDR
    Patch

    🚨 HIGH - snapd snap-confine seccomp sandbox confinement bypass (CVE-2026-15226) Canonical snapd contains a confinement bypass in the snap-confine component where the default seccomp templates don’t correctly block operations that can create or manipulate setuid execution flags inside strictly confined snaps. The root cause is a seccomp policy/template hardening gap (improper sandbox policy enforcement) that fails to prevent setuid binary creation/execution paths. An attacker who can execute code within a strictly confined snap can leverage these allowed operations to create or drop setuid binaries and then execute them to escape intended restrictions within the container namespace. If exploited, this can enable privileged actions beyond the snap’s confinement boundary, potentially leading to privilege escalation within the namespace and broader compromise depending on host integration. 👉 Affected: snapd (versions using default seccomp templates prior to the hardened template engine fix) | Upgrade to the vendor-fixed snapd release with hardened seccomp templates for CVE-2026-15226

    Post summary

    Canonical’s snapd has a seccomp sandbox flaw that lets confined snaps create and execute setuid binaries, enabling privilege escalation; Canonical has released a patched version with hardened templates and advises an upgrade.

    0000072
    255 followersView on X

Explore more