Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-69p6-gp5x-j269

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

CVSS 4.8 MediumEPSS 0.0023 · 13th percentile

Published by the GitHub Advisory Database at 25 Jul 2024, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/snapcore/snapdGo<2.622.62
Identifiers
GHSA-69p6-gp5x-j269 · CVE-2024-29069 · GO-2024-3009
Weakness (CWE)
CWE-59 · CWE-610
Tags
Published
25 Jul 2024
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

snapd versions prior to 2.62 (Go package github.com/snapcore/snapd) do not properly check the destination of symbolic links when extracting a snap. An attacker who can convince a user to install a malicious snap containing symbolic links at certain file paths could cause snapd to write the contents of the link's target into a world-readable directory, potentially exposing privileged information to unprivileged users. Upgrade to version 2.62 or later.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.8 Medium 3.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L CNA (canonical)
  • CISA KEV Not listed.
  • EPSS 0.0023, the 13th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:15 UTC First seen by agentprime
  2. 31 Oct 2026, 14:15 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.