https://patchthecve.com/CVEs with upgrade or downgrade fix stepshttps://patchthecve.com/cve/CVE-2024-29069.htmlhttps://patchthecve.com/cve/CVE-2024-29069.htmlWed, 17 Jun 2026 07:22:21 +0000MEDIUM 4.8: In snapd versions prior to 2.62, snapd failed to properly check the destination of symbolic links when extracting a snap. The snap format is a squashfs file-system image and so can contain symbolic links and other file types. Various file entries within the snap squashfs image (such as icons and dehttps://patchthecve.com/cve/CVE-2024-29068.htmlhttps://patchthecve.com/cve/CVE-2024-29068.htmlWed, 17 Jun 2026 07:22:21 +0000MEDIUM 5.8: In snapd versions prior to 2.62, snapd failed to properly check the file type when extracting a snap. The snap format is a squashfs file-system image and so can contain files that are non-regular files (such as pipes or sockets etc). Various file entries within the snap squashfs image (such as iconhttps://patchthecve.com/cve/CVE-2024-1724.htmlhttps://patchthecve.com/cve/CVE-2024-1724.htmlWed, 17 Jun 2026 07:04:52 +0000MEDIUM 6.3: In snapd versions prior to 2.62, when using AppArmor for enforcement of sandbox permissions, snapd failed to restrict writes to the $HOME/bin path. In Ubuntu, when this path exists, it is automatically added to the users PATH. An attacker who could convince a user to install a malicious snap which https://patchthecve.com/cve/CVE-2020-27352.htmlhttps://patchthecve.com/cve/CVE-2020-27352.htmlWed, 17 Jun 2026 03:09:09 +0000CRITICAL 9.3: When generating the systemd service units for the docker snap (and other similar snaps), snapd does not specify Delegate=yes - as a result systemd will move processes from the containers created and managed by these snaps into the cgroup of the main daemon within the snap itself when reloading systehttps://patchthecve.com/cve/CVE-2024-5138.htmlhttps://patchthecve.com/cve/CVE-2024-5138.htmlWed, 17 Jun 2026 08:15:16 +0000HIGH 8.1: The snapctl component within snapd allows a confined snap to interact with the snapd daemon to take certain privileged actions on behalf of the snap. It was found that snapctl did not properly parse command-line arguments, allowing an unprivileged user to trigger an authorised action on behalf of thhttps://patchthecve.com/cve/CVE-2022-3328.htmlhttps://patchthecve.com/cve/CVE-2022-3328.htmlWed, 17 Jun 2026 04:59:18 +0000HIGH 7.8: Race condition in snap-confine's must_mkdir_and_open_with_perms()https://patchthecve.com/cve/CVE-2023-1523.htmlhttps://patchthecve.com/cve/CVE-2023-1523.htmlWed, 17 Jun 2026 05:28:09 +0000CRITICAL 10.0: Using the TIOCLINUX ioctl request, a malicious snap could inject contents into the input of the controlling terminal which could allow it to cause arbitrary commands to be executed outside of the snap sandbox after the snap exits. Graphical terminal emulators like xterm, gnome-terminal and others arhttps://patchthecve.com/cve/CVE-2021-4120.htmlhttps://patchthecve.com/cve/CVE-2021-4120.htmlWed, 17 Jun 2026 04:19:04 +0000HIGH 8.2: snapd 2.54.2 fails to perform sufficient validation of snap content interface and layout paths, resulting in the ability for snaps to inject arbitrary AppArmor policy rules via malformed content interface and layout declarations and hence escape strict snap confinement. Fixed in snapd versions 2.54.https://patchthecve.com/cve/CVE-2021-44731.htmlhttps://patchthecve.com/cve/CVE-2021-44731.htmlWed, 17 Jun 2026 04:12:46 +0000HIGH 7.8: A race condition existed in the snapd 2.54.2 snap-confine binary when preparing a private mount namespace for a snap. This could allow a local attacker to gain root privileges by bind-mounting their own contents inside the snap's private mount namespace and causing snap-confine to execute arbitrary https://patchthecve.com/cve/CVE-2021-44730.htmlhttps://patchthecve.com/cve/CVE-2021-44730.htmlWed, 17 Jun 2026 04:12:46 +0000HIGH 7.8: snapd 2.54.2 did not properly validate the location of the snap-confine binary. A local attacker who can hardlink this binary to another location to cause snap-confine to execute other arbitrary binaries and hence gain privilege escalation. Fixed in snapd versions 2.54.3+18.04, 2.54.3+20.04 and 2.54https://patchthecve.com/cve/CVE-2021-3155.htmlhttps://patchthecve.com/cve/CVE-2021-3155.htmlWed, 17 Jun 2026 04:04:45 +0000LOW 3.8: snapd 2.54.2 and earlier created ~/snap directories in user home directories without specifying owner-only permissions. This could allow a local attacker to read information that should have been private. Fixed in snapd versions 2.54.3+18.04, 2.54.3+20.04 and 2.54.3+21.10.1https://patchthecve.com/cve/CVE-2020-11933.htmlhttps://patchthecve.com/cve/CVE-2020-11933.htmlWed, 17 Jun 2026 02:51:05 +0000HIGH 7.3: cloud-init as managed by snapd on Ubuntu Core 16 and Ubuntu Core 18 devices was run without restrictions on every boot, which a physical attacker could exploit by crafting cloud-init user-data/meta-data via external media to perform arbitrary changes on the device to bypass intended security mechanihttps://patchthecve.com/cve/CVE-2019-11503.htmlhttps://patchthecve.com/cve/CVE-2019-11503.htmlWed, 17 Jun 2026 02:13:02 +0000HIGH 7.5: snap-confine as included in snapd before 2.39 did not guard against symlink races when performing the chdir() to the current working directory of the calling user, aka a "cwd restore permission bypass."https://patchthecve.com/cve/CVE-2019-11502.htmlhttps://patchthecve.com/cve/CVE-2019-11502.htmlWed, 17 Jun 2026 02:13:02 +0000HIGH 7.5: snap-confine in snapd before 2.38 incorrectly set the ownership of a snap application to the uid and gid of the first calling user. Consequently, that user had unintended access to a private /tmp directory.https://patchthecve.com/cve/CVE-2019-7304.htmlhttps://patchthecve.com/cve/CVE-2019-7304.htmlWed, 17 Jun 2026 02:40:25 +0000CRITICAL 9.8: Canonical snapd before version 2.37.1 incorrectly performed socket owner validation, allowing an attacker to run arbitrary commands as root. This issue affects: Canonical snapd versions prior to 2.37.1.https://patchthecve.com/cve/CVE-2019-7303.htmlhttps://patchthecve.com/cve/CVE-2019-7303.htmlWed, 17 Jun 2026 02:40:25 +0000HIGH 7.5: A vulnerability in the seccomp filters of Canonical snapd before version 2.37.4 allows a strict mode snap to insert characters into a terminal on a 64-bit host. The seccomp rules were generated to match 64-bit ioctl(2) commands on a 64-bit platform; however, the Linux kernel only uses the lower 32 bhttps://patchthecve.com/cve/CVE-2017-14178.htmlhttps://patchthecve.com/cve/CVE-2017-14178.htmlWed, 17 Jun 2026 01:05:43 +0000HIGH 7.5: In snapd 2.27 through 2.29.2 the 'snap logs' command could be made to call journalctl without match arguments and therefore allow unprivileged, unauthenticated users to bypass systemd-journald's access restrictions.