CVE-2026-33997: Moby: Off-by-one error in plugin privilege validation

Published Mar 27, 2026
·
Updated

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)

Other sources

Moby is an open source container framework. Prior to version 29.3.1, 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. This issue has been patched in version 29.3.1.

MITRE

Affected Software

4 affected componentsFixes available
go/github.com/moby/moby/v2<2.0.0-beta.8
2.0.0-beta.8
go/github.com/moby/moby<29.3.1
go/github.com/docker/docker<29.3.1
Mobyproject Moby<29.3.1

Event History

Mar 27, 2026
Advisory Published
via GitHub·05:38 PM
Data Sourced
via GitHub·05:38 PM
DescriptionSeverityWeaknessAffected Software
Mar 31, 2026
CVE Published
via MITRE·01:36 AM
Data Sourced
via MITRE·01:36 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:15 AM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-33997?

CVE-2026-33997 has been classified as a high severity vulnerability due to its potential to allow privilege escalation.

2

How do I fix CVE-2026-33997?

To fix CVE-2026-33997, upgrade to the latest version of the affected software beyond 2.0.0-beta.8 or 29.3.1.

3

What types of software are affected by CVE-2026-33997?

CVE-2026-33997 affects specific versions of Docker and Moby packages, specifically under the versions specified.

4

Can CVE-2026-33997 be exploited by attackers?

Yes, CVE-2026-33997 can be exploited by attackers to bypass privilege validation during the installation of Docker plugins.

5

What are the implications of CVE-2026-33997 for Docker users?

The implications of CVE-2026-33997 include potential unauthorized access to system resources and risk of compromise.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203