Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Moby: Off-by-one error in plugin privilege validation

CVSS 3.1 6.8 MEDIUMEUVD CVSS 3.1 8.4 CVSS 3.1 · [email protected] · Secondary 6.8 MEDIUMCVSS 3.1 · [email protected] · Primary 8.1 HIGHCVSS 3.1 · 0b0ca135-0b70-47e7-9f44-1890c2a1c46c · Secondary 8.4 HIGHCVSS_V3 Publisher rating MODERATEFixed by github.com/moby/moby/v2 2.0.0-beta.8osv · severity unknownFixed by github.com/moby/moby/v2 2.0.0-beta.8KEV status unknown

cve-program · CVE-2026-33997

Published

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.

Read the publisher's advisory

euvd · EUVD-2026-17290

Published

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.

Read the publisher's advisory

nvd · CVE-2026-33997

Published

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.

Read the publisher's advisory

osv · GHSA-pxq6-2prw-chj9

Published

## 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 ([email protected], PGP 0x9FA5B73E)

Read the publisher's advisory

osv · GO-2026-4883

Published

Moby has an Off-by-one error in its plugin privilege validation in github.com/docker/docker

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-33997

Published

moby

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "moby",
                    "product": "moby",
                    "versions": [
                        {
                            "version": "< 29.3.1",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-17290

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Mar 31, 2026, 1:36:51 AM

dateUpdated: Sep 9, 2026, 12:04:48 PM

7 related source bulletins · separate from aliases

WID-SEC-W-2026-0873: docker: Mehrere Schwachstellen

CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33997 · CVE-2026-34040

RHSA-2026:22347: Red Hat Security Advisory: Multicluster Global Hub 1.4.5 security update

CVE-2026-4427 · CVE-2026-21728 · CVE-2026-25679 · CVE-2026-27137 · CVE-2026-27889 · CVE-2026-29785 · CVE-2026-32280 · CVE-2026-32281 · CVE-2026-32282 · CVE-2026-32283 · CVE-2026-32285 · CVE-2026-32286 · CVE-2026-33186 · CVE-2026-33215 · CVE-2026-33216 · CVE-2026-33217 · CVE-2026-33218 · CVE-2026-33219 · CVE-2026-33247 · CVE-2026-33413 · CVE-2026-33487 · CVE-2026-33810 · CVE-2026-33813 · CVE-2026-33997 · CVE-2026-34040 · CVE-2026-34986 · CVE-2026-40890 · CVE-2026-41602 · CVE-2026-41603 · CVE-2026-41604 · CVE-2026-41605 · CVE-2026-41606 · CVE-2026-41607 · CVE-2026-41636 · CVE-2026-43869

RHSA-2026:21769: Red Hat Security Advisory: Multicluster Global Hub 1.5.4 security update

CVE-2026-4427 · CVE-2026-21728 · CVE-2026-25679 · CVE-2026-27137 · CVE-2026-27889 · CVE-2026-29785 · CVE-2026-32280 · CVE-2026-32281 · CVE-2026-32282 · CVE-2026-32283 · CVE-2026-32285 · CVE-2026-32286 · CVE-2026-33186 · CVE-2026-33215 · CVE-2026-33216 · CVE-2026-33217 · CVE-2026-33218 · CVE-2026-33219 · CVE-2026-33247 · CVE-2026-33413 · CVE-2026-33487 · CVE-2026-33810 · CVE-2026-33813 · CVE-2026-33997 · CVE-2026-34040 · CVE-2026-34986 · CVE-2026-40890 · CVE-2026-41602 · CVE-2026-41603 · CVE-2026-41604 · CVE-2026-41605 · CVE-2026-41606 · CVE-2026-41607 · CVE-2026-41636 · CVE-2026-43869

openSUSE-SU-2026:11075-1: docker-stable-24.0.9_ce-18.1 on GA media

CVE-2026-33186 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33814 · CVE-2026-33997 · CVE-2026-34040 · CVE-2026-39821 · CVE-2026-41567

SUSE-SU-2026:2578-1: Security update for docker-stable

CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33997 · CVE-2026-34040

RHSA-2026:23345: Red Hat Security Advisory: Multicluster Global Hub 1.6.2 security update

CVE-2026-4427 · CVE-2026-21728 · CVE-2026-25679 · CVE-2026-27137 · CVE-2026-27889 · CVE-2026-29785 · CVE-2026-32280 · CVE-2026-32281 · CVE-2026-32282 · CVE-2026-32283 · CVE-2026-32285 · CVE-2026-32286 · CVE-2026-33186 · CVE-2026-33215 · CVE-2026-33216 · CVE-2026-33217 · CVE-2026-33218 · CVE-2026-33219 · CVE-2026-33247 · CVE-2026-33413 · CVE-2026-33487 · CVE-2026-33810 · CVE-2026-33813 · CVE-2026-33997 · CVE-2026-34040 · CVE-2026-34986 · CVE-2026-40890 · CVE-2026-41602 · CVE-2026-41603 · CVE-2026-41604 · CVE-2026-41605 · CVE-2026-41606 · CVE-2026-41607 · CVE-2026-41636 · CVE-2026-43869

openSUSE-SU-2026:21205-1: Security update for docker-stable

CVE-2026-33186 · CVE-2026-33814 · CVE-2026-33997 · CVE-2026-34040 · CVE-2026-39821 · CVE-2026-41567

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-33997

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-193 · CWE-266

Original publisher date fields

published: 2026-03-31T03:15:57.523

lastModified: 2026-09-09T13:19:32.963

1 source CPE criteria · context only
  • cpe:2.3:a:docker:engine:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-pxq6-2prw-chj9

Published

github.com/docker/docker

Go

SEMVER · introduced 0

github.com/moby/moby/v2

Go

SEMVER · introduced 0 → fixed 2.0.0-beta.8

github.com/moby/moby

Go

SEMVER · introduced 0

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2026-4883

Published

github.com/docker/docker

Go

SEMVER · introduced 0

github.com/moby/moby

Go

SEMVER · introduced 0

github.com/moby/moby/v2

Go

SEMVER · introduced 0 → fixed 2.0.0-beta.8

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 15 Nov 12:11 UTC · 256 of 275 readable · 252 fully read · documentation 469/469 current