NVD / CVE Program· CNA canonical

CVE-2024-29069: snapd will follow archived symlinks when unpacking a filesystem

HighCVSS 7.3 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 29/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. A user must open a link or visit a page. No special conditions are required; it is repeatable.
Fixed version: snapd (Debian:13) 2.62-1; github.com/snapcore/snapd (Go) 2.62.
Severity is disputed: the assigning authority (CNA) scores it 4.8, NVD 7.3.

Low priority for now. Upgrade to snapd (Debian:13) 2.62-1; github.com/snapcore/snapd (Go) 2.62 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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 desktop files etc) are directly read by snapd when it is extracted. An attacker who could convince a user to install a malicious snap which contained symbolic links at these paths could then cause snapd to write out the contents of the symbolic link destination into a world-readable directory. This in-turn could allow an unprivileged user to gain access to privileged information.

Local privilege escalation

Published: Jul 25, 2024
Updated: Jun 17, 2026
EPSS: 0.2% · 13th percentile
CWE: CWE-610

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 29 / 40 · 7.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.3
CNA · canonical: 4.8; 2.5 point gap

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
canonical	snapd	cpe:2.3:a:canonical:snapd

Versions reported by the vendor

Affected version ranges reported by the assigning authority (canonical). Independent of NVD's CPE analysis and usually ahead of it.

Canonical snapd
- before 2.62affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

canonical snapdbefore 2.62

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	snapd	from 0	—
Debian:13	snapd	before 2.62-1	2.62-1
Go	github.com/snapcore/snapd	from 0	—
Go	github.com/snapcore/snapd	before 2.62	2.62

Same product

canonical: all records

Other highest-scoring records for the same primary product.

CVE-2019-7304Local privilege escalation via snapd socket
57Plan
CVE-2023-1523Using the TIOCLINUX ioctl request, a malicious snap could inject contents into the input of the controlling terminal which could allow it…
40Plan
CVE-2020-27352When generating the systemd service units for the docker snap (and other similar snaps), snapd does not specify Delegate=yes - as a result…
35Monitor

Published before and after this one in the same product

← EarlierCVE-2024-5138May 31, 2024 · The snapctl component within snapd allows a confined snap to interact with the snapd daemon to take certain privileged actions on behalf of…
32Monitor
← EarlierCVE-2024-1724Jul 25, 2024 · snapd allows $HOME/bin symlink
32Monitor
← EarlierCVE-2024-29068Jul 25, 2024 · snapd non-regular file indefinite blocking read
26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
debian:snapd	2.62-1 · Debian:13	Package registry (OSV)
Go:github.com/snapcore/snapd	2.62	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.