Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

snapd will follow archived symlinks when unpacking a filesystem

CVSS 3.1 4.8 MEDIUMEUVD CVSS 3.1 4.8 CVSS 3.1 · [email protected] · Secondary 4.8 MEDIUMCVSS 3.1 · [email protected] · Primary 7.3 HIGHCVSS_V3 CVSS_V4 Publisher rating LOWFixed by github.com/snapcore/snapd 2.62osv · severity unknownKEV status unknown

cve-program · CVE-2024-29069

Published

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.

Read the publisher's advisory

euvd · EUVD-2024-2278

Published

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.

Read the publisher's advisory

nvd · CVE-2024-29069

Published

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.

Read the publisher's advisory

osv · GHSA-69p6-gp5x-j269

Published

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.

Read the publisher's advisory

osv · GO-2024-3009

Published

snapd failed to properly check the destination of symbolic links when extracting a snap in github.com/snapcore/snapd. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: github.com/snapcore/snapd before v2.62.0.

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

Risk history

Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).

Advisory history

14 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

15 Nov 2026 07:46:35 UTC

In snapd versions prior to 2.62, snapd failed to properly check the

euvd · EUVD-2024-2278 · Published

13 Nov 2026 07:11:11 UTC

In snapd versions prior to 2.62, snapd failed to properly check the

euvd · EUVD-2024-2278 · Published

11 Nov 2026 00:36:30 UTC

In snapd versions prior to 2.62, snapd failed to properly check the

euvd · EUVD-2024-2278 · Published

9 Nov 2026 00:07:18 UTC

In snapd versions prior to 2.62, snapd failed to properly check the

euvd · EUVD-2024-2278 · Published

6 Nov 2026 23:11:03 UTC

In snapd versions prior to 2.62, snapd failed to properly check the

euvd · EUVD-2024-2278 · Published

4 Nov 2026 22:57:28 UTC

In snapd versions prior to 2.62, snapd failed to properly check the

euvd · EUVD-2024-2278 · Published

2 Nov 2026 22:02:14 UTC

In snapd versions prior to 2.62, snapd failed to properly check the

euvd · EUVD-2024-2278 · Published

31 Oct 2026 21:08:10 UTC

In snapd versions prior to 2.62, snapd failed to properly check the

euvd · EUVD-2024-2278 · Published

29 Oct 2026 20:19:59 UTC

In snapd versions prior to 2.62, snapd failed to properly check the

euvd · EUVD-2024-2278 · Published

27 Oct 2026 19:51:41 UTC

In snapd versions prior to 2.62, snapd failed to properly check the

euvd · EUVD-2024-2278 · Published

24 Oct 2026 23:17:34 UTC

In snapd versions prior to 2.62, snapd failed to properly check the

nvd · CVE-2024-29069 · Published

24 Oct 2026 13:19:41 UTC

snapd failed to properly check the destination of symbolic links when extracting a snap

osv · GHSA-69p6-gp5x-j269 · Published

24 Oct 2026 13:19:41 UTC

snapd failed to properly check the destination of symbolic links when extracting a snap in github.com/snapcore/snapd

osv · GO-2024-3009 · Published

23 Oct 2026 15:48:27 UTC

snapd will follow archived symlinks when unpacking a filesystem

cve-program · CVE-2024-29069 · Published

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 14:56 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current