Snapd vulnerabilitiesRanked by how likely they are to be used.
Snapd is made by Canonical. We track 16 published vulnerabilities in it, across 275 versions. None of them is on the list of flaws known to be exploited today. If you run Snapd, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Snapd vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Snapd's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Snapd flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 61%CVE-2019-7304Critical
Canonical snapd before version 2.37.1 incorrectly performed socket owner validation, allowing an attacker to run arbitrary commands as root.
- 3.7%CVE-2019-7303High
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.
- 2.5%CVE-2019-11502High
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.
- 2.4%CVE-2019-11503High
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."
- 1.4%CVE-2023-1523Critical
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...
- 1.0%CVE-2021-44731High
A race condition existed in the snapd 2.54.2 snap-confine binary when preparing a private mount namespace for a snap.
- 0.8%CVE-2024-5138High
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.
- 0.4%CVE-2021-4120High
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...
- 0.4%CVE-2022-3328High
Race condition in snap-confine's must_mkdir_and_open_with_perms()
- 0.4%CVE-2021-44730High
snapd 2.54.2 did not properly validate the location of the snap-confine binary.
Running Snapd? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Snapd on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 16 published vulnerabilities listed under the name Snapd, across 275 versions.
None of Snapd's vulnerabilities is on the list of flaws known to be exploited today.
Create a EdgeProtect account and track Snapd. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.