🛡️ CVE-2026-33997 — engine
Description
Moby has an Off-by-one error in its plugin privilege validation
Summary
A security vulnerability has been detected that allows [plugins](https://docs.docker.com/engine/extend/legacy_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)
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is high, an attacker needs no privileges on the target. A user must be tricked into taking some action. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability none.
Weakness class
CVE-2026-33997 is classified as CWE-193: Off-by-one Error. A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value.
Affected software
CVE-2026-33997 is recorded against 5 packages.
- engine (fixed in 29.3.1)
- github.com/docker/docker
- github.com/moby/moby
- github.com/moby/moby/v2
- moby (fixed in 29.3.1)
Timeline and source
Published on 31 March 2026 and last revised on 10 August 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.
References
github.com
github.com
access.redhat.com
access.redhat.com
access.redhat.com
access.redhat.com
bugzilla.redhat.com
security.access.redhat.com
CVE-2026-33997 on other distributions
Each distribution ships its own build and its own fixed version. Pick the one you run:
Details
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| engine | — | 29.3.1 |
| github.com/docker/docker | — | — |
| github.com/moby/moby | — | — |
| github.com/moby/moby/v2 | — | — |
| moby | — | 29.3.1 |
References
Similar Threats
- Unknown CLSA-2026-1773015266
- Unknown CLSA-2026-1776818202
- Unknown CLSA-2026-1784856203
- High CVE-2026-59725
- High CVE-2026-59724
Vulnerability Monitoring
Track new vulnerabilities in engine
CVE-2026-33997 is rated CVSS 6.8 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.
Set Up Free Alerts →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.