<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 10:47:09 +0000</lastBuildDate>
    <item>
      <title>GHSA-pxq6-2prw-chj9 — Moby has an Off-by-one error in its plugin privilege validation</title>
      <link>https://db.gcve.eu/vuln/ghsa-pxq6-2prw-chj9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/docker/docker, Go: github.com/moby/moby/v2, Go: github.com/moby/moby&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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&amp;#39;s privilege comparison logic, the daemon may incorrectly accept a privilege set that differs from the one approved by the user.&lt;/p&gt;
&lt;p&gt;Plugins that request exactly one privilege are also affected, because no comparison is performed at all.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;**If plugins are not in use, there is no impact.**&lt;/p&gt;
&lt;p&gt;When a plugin is installed, the daemon computes the privileges required by the plugin&amp;#39;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.&lt;/p&gt;
&lt;p&gt;Anyone who depends on the plugin installation approval flow as a meaningful security boundary is potentially impacted.&lt;/p&gt;
&lt;p&gt;Depending on the privilege set involved, this may include highly sensitive plugin permissions such as broad device access.&lt;/p&gt;
&lt;p&gt;**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.**&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;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, foll…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/docker/docker, Go: github.com/moby/moby/v2, Go: github.com/moby/moby&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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&amp;#39;s privilege comparison logic, the daemon may incorrectly accept a privilege set that differs from the one approved by the user.&lt;/p&gt;
&lt;p&gt;Plugins that request exactly one privilege are also affected, because no comparison is performed at all.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;**If plugins are not in use, there is no impact.**&lt;/p&gt;
&lt;p&gt;When a plugin is installed, the daemon computes the privileges required by the plugin&amp;#39;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.&lt;/p&gt;
&lt;p&gt;Anyone who depends on the plugin installation approval flow as a meaningful security boundary is potentially impacted.&lt;/p&gt;
&lt;p&gt;Depending on the privilege set involved, this may include highly sensitive plugin permissions such as broad device access.&lt;/p&gt;
&lt;p&gt;**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.**&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;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, foll…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-pxq6-2prw-chj9</guid>
    </item>
  </channel>
</rss>
