CVE-2026-15226

HIGHPre-NVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-07-21. a secondary CVSS source baseline 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: None knownExposed: 0

A fix is available — apply it.

A sandbox confinement bypass vulnerability exists in Canonical snapd within its internal execution environment compiler (snap-confine). The default seccomp security templates generated by the engine to restrict system calls do not filter or reject process operations capable of creating or manipulating file execution flags with set-user-ID attributes. Consequently, an application running within a strictly confined snap environment can successfully compile or drop binaries and apply setuid properties to them. If a compromised or malicious process inside the snap sandbox executes these generated setuid binaries, it can potentially circumvent architectural sandboxing assumptions, drop intended restriction policies, or execute privileged actions inside the container namespace that should otherwise be strictly blocked. The vulnerability has been resolved by hardening the seccomp template engine to block the execution and creation of setuid executables by sandboxed snap processes.

CVSS v3
8.4
EG Score
8.4(medium)
EG Risk
38(Track)
EG Risk 38/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
Severity84% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 22, 2026

References (1)

Vendor Advisories for CVE-2026-15226(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuubuntu-snappy-cli (2.76+ubuntu22.04.1) @ jammy2026-09-11ubuntu

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.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 22× in last 7d / 123× 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 226 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-15226?
CVE-2026-15226 is a high vulnerability published on July 21, 2026. A sandbox confinement bypass vulnerability exists in Canonical snapd within its internal execution environment compiler (snap-confine). The default seccomp security templates generated by the engine to restrict system calls do not filter or reject process operations capable of creating or…
When was CVE-2026-15226 disclosed?
CVE-2026-15226 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-2026-15226 actively exploited?
CVE-2026-15226 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 95.1% of all scored CVEs.
What is the CVSS score of CVE-2026-15226?
CVE-2026-15226 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-15226?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15226, 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-2026-15226

Explore →

Is Your Infrastructure Affected by CVE-2026-15226?

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

Start Free Scan →Browse All CVEs