MediumGHSA-pxq6-2prw-chj9CVE-2026-33997GO-2026-4883

Moby has an Off-by-one error in its plugin privilege validation

Published 27 Mar 2026 · Updated 10 Sept 2026

Is your project on an affected github.com/docker/docker?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
All versions
Fixed in
No fix released
Affected
<2.0.0-beta.8
Fixed in
2.0.0-beta.8
Update to the fixed version for your release line, for example:go get github.com/moby/moby/v2@v2.0.0-beta.8
Affected
All versions
Fixed in
No fix released

Details

Summary

A security vulnerability has been detected that allows plugins privilege validation to be bypassed during docker plugin install. Due to an error in the daemon's privilege comparison logic, the daemon may incorrectly accept a privilege set that differs from the one approved by the user.

Plugins that request exactly one privilege are also affected, because no comparison is performed at all.

Impact

If plugins are not in use, there is no impact.

When a plugin is installed, the daemon computes the privileges required by the plugin's configuration and compares them with the privileges approved during installation. A malicious plugin can exploit this bug so that the daemon accepts privileges that differ from what was intended to be approved.

Anyone who depends on the plugin installation approval flow as a meaningful security boundary is potentially impacted.

Depending on the privilege set involved, this may include highly sensitive plugin permissions such as broad device access.

For consideration: exploitation still requires a plugin to be installed from a malicious source, and Docker plugins are relatively uncommon. Docker Desktop also does not support plugins.

Workarounds

If unable to update immediately:

  • Do not install plugins from untrusted sources
  • Carefully review all privileges requested during docker plugin install
  • Restrict access to the Docker daemon to trusted parties, following the principle of least privilege
  • Avoid relying on plugin privilege approval as the only control boundary for sensitive environments

Credits

  • Reported by Cody (c@wormhole.guru, PGP 0x9FA5B73E)

Is GHSA-pxq6-2prw-chj9 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/docker/docker, and gives you the command that fixes it.

More advisories for github.com/docker/docker

  • LowCVE-2026-41568Race condition in 'docker cp' in github.com/docker/docker allows creation of arbitrary files · 25 Jun 2026
  • LowCVE-2026-41567Docker: 'PUT /containers/{id}/archive' executes container binary on the host in github.com/docker/docker · 25 Jun 2026
  • LowCVE-2026-42306Race condition in 'docker cp' in github.com/docker/docker allows bind mount redirection · 25 Jun 2026
  • HighCVE-2026-42306Docker: Race condition in docker cp allows bind mount redirection to host path · 18 May 2026
  • MediumCVE-2026-41568Docker: Race condition in docker cp allows creation of arbitrary empty files on the host via symlink swap · 18 May 2026
  • HighCVE-2026-41567Docker: `PUT /containers/{id}/archive` executes container binary on the host · 18 May 2026
All 66 advisories for github.com/docker/docker

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.