CVE-2024-5300: AppArmor base profile access control bypass in snapd exposing hashed passwords via systemd-userdbd
CVE-2024-5300 is an access control bypass and information disclosure vulnerability in Canonical snapd caused by an overly permissive base AppArmor profile. The abstraction rules in the nss-systemd AppArmor abstraction inherited by snap confinement allow strictly confined snap applications to access the systemd-userdbd Varlink sockets used for user database queries. On systems where systemd-userdbd is installed and running, the service does not distinguish between an unconfined host root context and a root process executing inside a snap sandbox. As a result, a strictly confined snap component running as root, such as a daemon or configuration hook, can query the userdb interface and obtain complete user records, including hashed passwords normally protected in the shadow database. The flaw therefore breaks intended snap sandbox isolation and exposes sensitive authentication material to code that should not have access to it.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows a local attacker controlling a strictly confined snap that executes as root to bypass intended snap confinement and disclose sensitive system information. The primary impact is exposure of complete user records, including hashed password data from the shadow database, for local accounts on the host. This can materially aid offline password cracking, credential recovery, and follow-on privilege abuse against the affected system or related environments where recovered credentials are reused.
Mitigation
If you can’t patch tonight, do this now.
The issue is mitigated if systemd-userdbd is not installed or not operational, which reduces or removes the exposed attack surface. Where immediate patching is not possible, limiting deployment of strictly confined snaps that run as root and disabling or avoiding the affected userdb service where operationally feasible can reduce risk until fixed packages are installed.
Remediation
Patch, then assume compromise.
Update snapd to a fixed version provided by the vendor for the affected Ubuntu release. Reported fixed package versions include 2.76+ubuntu26.04.3 for Ubuntu 26.04 LTS, 2.76+ubuntu24.04.1 for Ubuntu 24.04 LTS, 2.76+ubuntu22.04.1 for Ubuntu 22.04 LTS, 2.67.1+20.04ubuntu1~esm3 for Ubuntu 20.04 LTS, 2.61.4ubuntu0.18.04.1+esm4 for Ubuntu 18.04 LTS, and 2.61.4ubuntu0.16.04.1+esm4 for Ubuntu 16.04 LTS. Applying standard system updates and rebooting to ensure the updated snapd confinement policy is active is advised.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Frequently asked questions
- Is CVE-2024-5300 exploited in the wild?
- As of Sep 25, 2026, Mallory has no reports of CVE-2024-5300 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2024-5300?
- As of Sep 25, 2026, Mallory has found no public exploit for CVE-2024-5300.
- Is there a patch for CVE-2024-5300?
- Update snapd to a fixed version provided by the vendor for the affected Ubuntu release. Reported fixed package versions include 2.76+ubuntu26.04.3 for Ubuntu 26.04 LTS, 2.76+ubuntu24.04.1 for Ubuntu 24.04 LTS, 2.76+ubuntu22.04.1 for Ubuntu 22.04 LTS, 2.67.1+20.04ubuntu1~esm3 for Ubuntu 20.04 LTS, 2.61.4ubuntu0.18.04.1+esm4 for Ubuntu 18.04 LTS, and 2.61.4ubuntu0.16.04.1+esm4 for Ubuntu 16.04 LTS.
- How severe is CVE-2024-5300?
- CVE-2024-5300 has a CVSS v3.1 score of 5.6 (Medium) and an EPSS score of 0.13% (3rd percentile) as of Sep 25, 2026.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.