Github.com/snapcore/snapd
5 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Github.com/snapcore/snapd, a product in the oss libraries space. Use it to gauge the current risk picture and drill into individual advisories.
Github.com/snapcore/snapd CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 0 |
Severity
How the 5 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- High2
- Medium3
Latest CVEs
The 5 most recently published vulnerabilities affecting Github.com/snapcore/snapd.
- CVE-2024-29069snapd will follow archived symlinks when unpacking a filesystem4.8
- CVE-2024-29068snapd non-regular file indefinite blocking read5.8
- CVE-2024-1724snapd allows $HOME/bin symlink6.3
- CVE-2024-5138The 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 pars...8.1
- CVE-2022-3328Race condition in snap-confine's must_mkdir_and_open_with_perms()7.8
Product grouping is registry-driven, with AI assist and human review. How it works