CVE-2024-1724 is a medium severity (CVSS 6.3) flaw in snapd versions before 2.62. When AppArmor enforces sandbox permissions, snapd failed to restrict writes to the HOME/bin path, which Ubuntu adds to the user's PATH. The fix is snapd 2.62 or later.
What's affected
The record says snapd versions prior to 2.62 are affected when using AppArmor for enforcement of sandbox permissions. An attacker who could convince a user to install a malicious snap that uses the home plug could install scripts into the user's PATH and have them run outside the sandbox. The references are the fix commit, a pull request (13689) and a write up by the researcher.
The NVD score is 6.3 (medium) with vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L. The weakness is CWE-732 (incorrect permission assignment for critical resource).
How to check if you're exposed
Check the snapd version on each host.
snap version
Anything before 2.62 is affected. The path only matters if it exists, so also check whether the directory is present in user home directories.
ls -ld "$HOME/bin"
On Ubuntu the directory is added to PATH when it exists. Review which snaps use the home plug.
What to do now
- Update snapd to 2.62 or later with your distribution's package manager.
- Review installed snaps and remove ones you do not recognize or trust.
- Only install snaps from publishers you trust.
- Check the contents of the user bin directory for scripts you did not create.
- Include snapd in your regular patching, since it runs on many desktops.
Why it matters
The sandbox is the point of a snap. If a snap with permission to the home directory can write into a directory that is in the user's PATH, then something the user runs later is no longer confined. It is a privilege boundary issue rather than a code execution bug in the usual sense.
It is rated medium because it needs the user to install a malicious snap first and the home plug to be present. Not listed as exploited. Safeguard's free in-browser dependency scan at gold.safeguard.sh/scan can show whether a component tied to this CVE appears in your dependency manifests. The Gold directory keeps the record, severity and references in one place, and reachability analysis helps you separate code paths that can actually be hit from packages that are merely installed.
Quick check
What is the fixed version?
snapd 2.62, according to the record.
Sources
Last reviewed: 19 October 2026.
