VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

snapd: vulnerability history, versions and safety

snapd is a package in the Debian ecosystem. Vulert records 33 vulnerabilities for it across 40 releases, from Nov -0001 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
33 vulnerabilities recorded U33
i
10 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
3 in the last 12 months

Most recent disclosure 21 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all snapd vulnerabilities

Vulert verdict on snapd i

Updated on 23 Oct 2026

Careful: 10 of the 33 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 33 vulnerabilities on record across 2026 years, 3 in the last year.

What to do: Plan around the 10 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 33 over 2026 years · 3 in the last year i
  • Latest disclosure 21 Jul 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 10 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for snapd, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 40 of 40 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 1
  • 2018 2
  • 2019 8
  • 2020 2
  • 2022 8
  • 2023 1
  • 2024 8
  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 33 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for snapd

The 5 most severe of 33 vulnerabilities recorded for this package

Search all 33 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Arbitrary Command Execution Vulnerability in Snapd Package 10.0 critical No fix published 01 Sep 2023
Critical Socket Owner Validation Flaw in Canonical Snapd 9.8 critical 2.37.1-1 23 Apr 2019
Privilege Escalation Risk in Docker Snap due to Incomplete Systemd Configuration in Snapd 8.8 high 2.49-1 21 Jun 2024
Privilege Escalation Vulnerability in Snapd: CVE-2021-44730 8.8 high 2.49-1+deb11u1 17 Feb 2022
Snapd Vulnerability: Arbitrary Script Installation via Home Path Exposure 8.2 high No fix published 25 Jul 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About snapd

Is snapd safe to use?

Vulert records 33 vulnerabilities for snapd in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 33 not yet rated. 10 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does snapd have?

33 vulnerabilities are recorded for snapd in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 33 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new snapd vulnerabilities disclosed?

3 vulnerabilities were recorded for snapd in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of snapd are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor snapd for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the snapd version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.