Is CVE-2024-5300 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2024-5300 being exploited in the wild.

How severe is CVE-2024-5300?

Medium severity, with a CVSS score of 5.6, published 21 July 2026.

Which products and versions are affected?

Canonical Snapd before 2.76.1; Canonical Ubuntu before 2.76+ubuntu26.04.3.

Is there a fix for CVE-2024-5300?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2024-5300 attacked?

It is attacked with local access, in an operating system.

Am I affected by CVE-2024-5300?

Check whether you run Canonical Snapd or Canonical Ubuntu at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2024-5300: Canonical snapd access control bypass in AppArmor configuration

CVE-2024-5300 · Severity: medium · CVSS 5.6 · Published 2026-07-21

A security flaw in the AppArmor configuration for Canonical snapd allows restricted applications to bypass sandbox protections. If a malicious application is installed as a 'snap' and gains administrative privileges within its own container, it can steal sensitive system password hashes from the host computer. This could allow an attacker to perform offline password cracking to gain full control over other user accounts on the system.

Technologies: Canonical Snapd, Canonical Ubuntu. Vendors: Canonical.

Quick answers

Is CVE-2024-5300 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2024-5300 being exploited in the wild.
How severe is CVE-2024-5300?: Medium severity, with a CVSS score of 5.6, published 21 July 2026.
Which products and versions are affected?: Canonical Snapd before 2.76.1; Canonical Ubuntu before 2.76+ubuntu26.04.3.
Is there a fix for CVE-2024-5300?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2024-5300 attacked?: It is attacked with local access, in an operating system.
Am I affected by CVE-2024-5300?: Check whether you run Canonical Snapd or Canonical Ubuntu at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An access control bypass exists in the AppArmor abstraction rules for nss-systemd within Canonical snapd. The vulnerability stems from rules in /etc/apparmor.d/abstractions/nss-systemd that inadvertently allow strictly confined snaps to communicate with io.systemd.Multiplexer and io.systemd.NameServiceSwitch UNIX domain sockets. When the systemd-userdbd service is active, it fails to differentiate between host-level root users and restricted root users within a snap sandbox. A malicious snap running as root can query the Varlink interface to retrieve complete user records, including sensitive hashed passwords from /etc/shadow. This issue is mitigated by the fact that systemd-userdbd is not installed by default on standard Ubuntu deployments. Patches are available in snapd version 2.76.1 and corresponding Ubuntu package updates.

Affected products

Canonical snapd before 2.76.1
Canonical Ubuntu 26.04 LTS before 2.76+ubuntu26.04.3
Canonical Ubuntu 24.04 LTS before 2.76+ubuntu24.04.1
Canonical Ubuntu 22.04 LTS before 2.76+ubuntu22.04.1
Canonical Ubuntu 20.04 LTS before 2.67.1+20.04ubuntu1~esm2

Timeline

2026-07-21: advisory
2026-07-21: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.