Safeguard
Vulnerability Analysis•

CVE-2020-27352: Critical Container Privilege Flaw in snapd Docker Snap

CVE-2020-27352 is a critical snapd flaw that can move container processes into the main snap cgroup. Update snapd to 2.48.3 or later and refresh snaps.

Safeguard Security Team
3 min read

CVE-2020-27352 is a critical (CVSS 9.3) flaw in snapd. It did not set Delegate=yes in systemd units for the docker snap and similar snaps, so systemd could move container processes into the snap daemon's cgroup on reload. That may grant a container more privilege than intended. The fix is snapd 2.48.3.

What's affected

  • snapd on affected Ubuntu releases, including 16.04 and 18.04 LTS in the record's product list.
  • Fixed: snapd 2.48.3, per the Launchpad bug. Ubuntu's notice is USN-4728-1; I could not retrieve it, so confirm package versions there.
  • The fix does not apply to running containers: refresh affected snaps and restart containers.
  • Affected public snaps listed include docker, kubernetes-worker, aws-iot-greengrass (1.8.x track) and microk8s.

The record scores it 9.3 (Critical) with vector CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. The record does not flag it as a CISA Known Exploited Vulnerability, and none of the pages I read report exploitation in the wild.

How to check if you're exposed

Run snap version to see the snapd version, and snap list to see installed snaps such as docker or microk8s. A snapd older than 2.48.3 on a host with container snaps needs an update.

What to do now

  1. Update snapd through the system package manager or let the snap refresh run.
  2. Run snap version to confirm 2.48.3 or later.
  3. Refresh affected snaps so their units regenerate.
  4. Restart the containers, since running ones keep the old placement.
  5. Snap authors can add an assumes line for snapd2.48.3.

After you patch, record the new version for snapd in your asset inventory, and confirm it with the same check you used above. A fix that was never verified is easy to forget, and an inventory that shows versions is what lets you answer the next advisory in minutes instead of days.

Why it matters

The record maps this to CWE-269, improper privilege management. Without the delegate setting, systemd reorganizes the processes in a control group when units reload, and a container ends up inside the daemon's own group. The limits and isolation set around the container may no longer apply.

The maintainers' fix is to write Delegate=true into generated units for the container interfaces. If you run containers from snaps, patch the host and recycle the containers.

To check open source components in your own projects for known CVEs like this one, try the free in-browser dependency scan at gold.safeguard.sh/scan, or look the CVE up in the Gold directory.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Does updating snapd protect already running containers?

No. The Launchpad bug says the fix does not apply to running containers. Refresh affected snaps and restart the containers.

How do I find every place snapd is used?

Start with an inventory of installed software and versions, because you cannot patch what you have not found. Check servers, build hosts, test copies and anything a vendor bundles. For open source libraries, a dependency scan or SBOM gives the same list for your code.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.