CVE-2024-5138

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.8% (55th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 8.1Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

The snapctl component within snapd allows a confined snap to interact with the snapd daemon to take certain privileged actions on behalf of the snap. It was found that snapctl did not properly parse command-line arguments, allowing an unprivileged user to trigger an authorised action on behalf of the snap that would normally require administrator privileges to perform. This could possibly allow an unprivileged user to perform a denial of service or similar.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100CISA SSVC

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
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.8%
EPSS %ILE
56th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

May 31, 2024

Last Modified

August 26, 2025

Advisory Details (4)

Auto-updated Sep 19, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
generic
https://www.cve.org/CVERecord?id=CVE-2024-5138
githubMentions a patch (unverified)

CVE-2024-5138: snapd snapctl auth bypass · Advisory · canonical/snapd · GitHub

https://github.com/snapcore/snapd/security/advisories/GHSA-p9v8-q5m4-pf46
github_commit Patch Available

commit 68ee9c6aa916 (snapcore/snapd)

Patch available: snapcore/snapd 2.65.1 (contains commit 68ee9c6aa916)

https://github.com/snapcore/snapd/commit/68ee9c6aa916ab87dbfd9a26030690f2cabf1e14
generic🟡 PoC Available

Bug #2065077 “Security: snapd snapctl Auth Bypass” : Bugs : snapd

https://bugs.launchpad.net/snapd/+bug/2065077

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
snapd2.49-1 ... 2.76-1 (40 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
snapd2.57.6-1 ... 2.76.3-2 (35 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
snapd—
  • every version up to 2.62-3: fixed in 2.62-3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
snapd—
  • every version up to 2.62-3: fixed in 2.62-3
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/snapcore/snapd—
  • 2.51.6 up to 2.63.1: fixed in 2.63.1
  • every version up to 0.0.0-20240524114846-68ee9c6aa916: fixed in 0.0.0-20240524114846-68ee9c6aa916
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 30× 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 181 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2024-5138?
CVE-2024-5138 is a high vulnerability published on May 31, 2024. The snapctl component within snapd allows a confined snap to interact with the snapd daemon to take certain privileged actions on behalf of the snap. It was found that snapctl did not properly parse command-line arguments, allowing an unprivileged user to trigger an authorised action on behalf of…
When was CVE-2024-5138 disclosed?
CVE-2024-5138 was first published on May 31, 2024, with the most recent update on August 26, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-5138 actively exploited?
CVE-2024-5138 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-5138?
CVE-2024-5138 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2024-5138?
A fix for CVE-2024-5138 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-5138?

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

Book a Demo →Browse All CVEs