CVE-2024-5300

MEDIUMPre-NVD 5.65.6—
EchelonGraph scoreMEDIUM confidence

Score 5.6 from GitHub Security Advisory published 2026-07-21. a secondary CVSS source baseline 5.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
5.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.6Exploit: None knownExposed: 0

A fix is available — apply it.

An access control bypass and information disclosure vulnerability exists in the base AppArmor security profile configuration of Canonical snapd. The abstraction rules located in /etc/apparmor.d/abstractions/nss-systemd (inherited via ) inadvertently permit strictly confined snap applications, which lack the privileged account-control interface, to interact directly with the io.systemd.Multiplexer and io.systemd.NameServiceSwitch UNIX domain sockets under /run/systemd/userdb/. On systems where the systemd-userdbd service is installed and operational, the service fails to distinguish between an unconfined root user on the host system and a restricted root user running within a snap application's sandbox (such as a daemon or configuration hook). Because systemd-userdbd returns "complete" user records—including sensitive hashed user passwords from /etc/shadow—when queried by a process running as root, a compromised or malicious strictly confined snap executing code as root can successfully query the Varlink interface to retrieve all system password hashes, bypassing intended snap sandbox restrictions. This issue is mitigated by the fact that systemd-userdbd is not installed by default on standard Ubuntu deployments.

CVSS v3
5.6
EG Score
5.6(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity56% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 22, 2026

References (1)

Vendor Advisories for CVE-2024-5300(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuubuntu-snappy-cli (2.76+ubuntu22.04.1) @ jammy2026-09-11ubuntu
redhatsystemd-main-261-2.hum12026-06-24redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
snapd2.49-1 ... 2.76-1 (40 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
snapd2.57.6-1 ... 2.76.3-2 (35 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
snapd2.68.3-3 ... 2.76.3-2 (14 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
snapd2.68.3-3 ... 2.76-1 (11 versions)2.76.3-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 21× in last 7d / 89× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 165 total refreshes for this CVE.

  1. 2026-09-11 14:51 UTCEPSS rescore
  2. 2026-09-11 09:35 UTCEPSS rescore
  3. 2026-09-11 09:06 UTCEG score recompute
  4. 2026-09-11 09:06 UTCVendor advisory
  5. 2026-09-11 09:06 UTCGHSA enrichment
  6. 2026-09-10 09:33 UTCEPSS rescore
  7. 2026-09-09 11:33 UTCEG score recompute
  8. 2026-09-09 11:33 UTCVendor advisory
  9. 2026-09-09 11:33 UTCGHSA enrichment
  10. 2026-09-08 21:59 UTCEPSS rescore
  11. 2026-09-07 22:39 UTCEG score recompute
  12. 2026-09-07 22:39 UTCVendor advisory
  13. 2026-09-07 22:39 UTCGHSA enrichment
  14. 2026-09-07 16:00 UTCEPSS rescore
  15. 2026-09-06 13:46 UTCEPSS rescore
  16. 2026-09-06 11:00 UTCEG score recompute
  17. 2026-09-06 11:00 UTCVendor advisory
  18. 2026-09-06 11:00 UTCGHSA enrichment
  19. 2026-09-05 09:04 UTCEG score recompute
  20. 2026-09-05 09:04 UTCVendor advisory
  21. 2026-09-05 09:04 UTCGHSA enrichment
  22. 2026-09-04 13:59 UTCEPSS rescore
  23. 2026-09-04 05:05 UTCEPSS rescore
  24. 2026-09-02 00:58 UTCEG score recompute
  25. 2026-09-02 00:58 UTCVendor advisory
Show 75 more
  1. 2026-09-02 00:58 UTCGHSA enrichment
  2. 2026-09-01 13:52 UTCEPSS rescore
  3. 2026-08-31 01:46 UTCEG score recompute
  4. 2026-08-31 01:46 UTCVendor advisory
  5. 2026-08-31 01:46 UTCGHSA enrichment
  6. 2026-08-30 19:16 UTCEPSS rescore
  7. 2026-08-30 19:16 UTCEPSS rescore
  8. 2026-08-30 02:18 UTCEG score recompute
  9. 2026-08-30 02:18 UTCVendor advisory
  10. 2026-08-30 02:18 UTCGHSA enrichment
  11. 2026-08-28 21:39 UTCEPSS rescore
  12. 2026-08-27 21:18 UTCEG score recompute
  13. 2026-08-27 21:18 UTCVendor advisory
  14. 2026-08-27 21:18 UTCGHSA enrichment
  15. 2026-08-27 14:24 UTCEPSS rescore
  16. 2026-08-26 21:31 UTCEG score recompute
  17. 2026-08-26 21:31 UTCVendor advisory
  18. 2026-08-26 21:31 UTCGHSA enrichment
  19. 2026-08-26 14:44 UTCEPSS rescore
  20. 2026-08-25 19:59 UTCVendor advisory
  21. 2026-08-25 19:59 UTCGHSA enrichment
  22. 2026-08-24 20:23 UTCEG score recompute
  23. 2026-08-24 20:23 UTCVendor advisory
  24. 2026-08-24 20:23 UTCGHSA enrichment
  25. 2026-08-24 14:15 UTCEPSS rescore
  26. 2026-08-23 20:56 UTCVendor advisory
  27. 2026-08-23 20:56 UTCGHSA enrichment
  28. 2026-08-22 21:27 UTCVendor advisory
  29. 2026-08-22 21:27 UTCGHSA enrichment
  30. 2026-08-21 21:41 UTCEG score recompute
  31. 2026-08-21 21:41 UTCVendor advisory
  32. 2026-08-21 21:41 UTCGHSA enrichment
  33. 2026-08-20 22:54 UTCEPSS rescore
  34. 2026-08-20 22:13 UTCEG score recompute
  35. 2026-08-20 22:13 UTCVendor advisory
  36. 2026-08-20 22:13 UTCGHSA enrichment
  37. 2026-08-19 22:40 UTCEG score recompute
  38. 2026-08-19 22:40 UTCVendor advisory
  39. 2026-08-19 22:40 UTCGHSA enrichment
  40. 2026-08-19 17:02 UTCEPSS rescore
  41. 2026-08-18 21:49 UTCVendor advisory
  42. 2026-08-18 21:48 UTCGHSA enrichment
  43. 2026-08-17 22:14 UTCEG score recompute
  44. 2026-08-17 22:14 UTCVendor advisory
  45. 2026-08-17 22:14 UTCGHSA enrichment
  46. 2026-08-17 13:45 UTCEPSS rescore
  47. 2026-08-16 22:47 UTCEG score recompute
  48. 2026-08-16 22:47 UTCVendor advisory
  49. 2026-08-16 22:47 UTCGHSA enrichment
  50. 2026-08-16 14:55 UTCEPSS rescore
  51. 2026-08-16 02:13 UTCEPSS rescore
  52. 2026-08-15 23:20 UTCEG score recompute
  53. 2026-08-15 23:20 UTCVendor advisory
  54. 2026-08-15 23:20 UTCGHSA enrichment
  55. 2026-08-15 01:29 UTCEPSS rescore
  56. 2026-08-14 23:52 UTCVendor advisory
  57. 2026-08-14 23:52 UTCGHSA enrichment
  58. 2026-08-14 00:25 UTCEG score recompute
  59. 2026-08-14 00:25 UTCVendor advisory
  60. 2026-08-14 00:25 UTCGHSA enrichment
  61. 2026-08-13 21:59 UTCEPSS rescore
  62. 2026-08-13 00:57 UTCEG score recompute
  63. 2026-08-13 00:57 UTCVendor advisory
  64. 2026-08-13 00:57 UTCGHSA enrichment
  65. 2026-08-12 13:49 UTCEPSS rescore
  66. 2026-08-12 01:29 UTCEG score recompute
  67. 2026-08-12 01:29 UTCVendor advisory
  68. 2026-08-12 01:29 UTCGHSA enrichment
  69. 2026-08-11 13:41 UTCEPSS rescore
  70. 2026-08-11 02:02 UTCVendor advisory
  71. 2026-08-11 02:02 UTCGHSA enrichment
  72. 2026-08-10 02:34 UTCEG score recompute
  73. 2026-08-10 02:34 UTCVendor advisory
  74. 2026-08-10 02:34 UTCGHSA enrichment
  75. 2026-08-09 13:45 UTCEPSS rescore

Frequently asked(5)

What is CVE-2024-5300?
CVE-2024-5300 is a medium vulnerability published on July 21, 2026. An access control bypass and information disclosure vulnerability exists in the base AppArmor security profile configuration of Canonical snapd. The abstraction rules located in /etc/apparmor.d/abstractions/nss-systemd (inherited via ) inadvertently permit strictly confined snap applications, which…
When was CVE-2024-5300 disclosed?
CVE-2024-5300 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-5300 actively exploited?
CVE-2024-5300 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.1% of all scored CVEs.
What is the CVSS score of CVE-2024-5300?
CVE-2024-5300 has a CVSS v3 base score of 5.6 (NVD).
How do I remediate CVE-2024-5300?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-5300, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-5300

Explore →

Is Your Infrastructure Affected by CVE-2024-5300?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs