<?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://cve.radiocsirt.org</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>Sun, 22 Nov 2026 13:37:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-129316 — Dokploy: serviceId lets a member reach any container (Member -&gt; Root) over the docker WebSocket handlers</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-129316</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; dokploy&lt;/p&gt;
&lt;p&gt;Dokploy is a free, self-hostable Platform as a Service (PaaS). From 0.29.13 until 0.31.0, the Docker terminal, container-log, and monitoring WebSocket handlers accept a caller-controlled serviceId as authorization but do not consistently bind the requested containerId or appName to that service. A member with read access to any service can consequently target unrelated containers, obtain a root shell in the Dokploy panel container, read other tenants&amp;#39; logs and statistics, and use the mounted Docker socket to compromise the host. This issue is fixed in version 0.31.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; dokploy&lt;/p&gt;
&lt;p&gt;Dokploy is a free, self-hostable Platform as a Service (PaaS). From 0.29.13 until 0.31.0, the Docker terminal, container-log, and monitoring WebSocket handlers accept a caller-controlled serviceId as authorization but do not consistently bind the requested containerId or appName to that service. A member with read access to any service can consequently target unrelated containers, obtain a root shell in the Dokploy panel container, read other tenants&amp;#39; logs and statistics, and use the mounted Docker socket to compromise the host. This issue is fixed in version 0.31.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-129316</guid>
    </item>
  </channel>
</rss>
