<?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>Tue, 06 Oct 2026 05:25:20 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-324249</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-324249</link>
      <description>EUVD-2026-324249</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-324249</guid>
    </item>
    <item>
      <title>fkie_cve-2026-35202</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-35202</link>
      <description>&lt;p&gt;Pterodactyl is a free, open-source game server management panel. Prior to version 1.12.3, the Pterodactyl Client API has a logic flaw that lets users bypass their assigned limits for database allocations. This happens because the database locking mechanism used in the controllers is totally broken and doesn&amp;#39;t actually lock anything. Version 1.12.3 patches the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Pterodactyl is a free, open-source game server management panel. Prior to version 1.12.3, the Pterodactyl Client API has a logic flaw that lets users bypass their assigned limits for database allocations. This happens because the database locking mechanism used in the controllers is totally broken and doesn&amp;#39;t actually lock anything. Version 1.12.3 patches the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-35202</guid>
    </item>
    <item>
      <title>GHSA-fgmm-w5cx-vrfw — Pterodactyl has a database resource limit bypass via race condition in Client API</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fgmm-w5cx-vrfw</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: pterodactyl/panel&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The Pterodactyl Client API has a logic flaw that lets users bypass their assigned limits for database allocations. This happens because the database locking mechanism used in the controllers is totally broken and doesn&amp;#39;t actually lock anything.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Inside `DatabaseController.php`, the code tries to prevent multiple databases from being created at once by calling `$server-&amp;gt;databases()-&amp;gt;lockForUpdate()`. In Laravel, this just configures a query builder but never actually sends a command to the database because it’s missing a terminal method like `count()` or `get()`. It’s basically a no-op that does nothing.&lt;/p&gt;
&lt;p&gt;Since there’s no real lock, multiple requests hitting the endpoint at the exact same time will all see that the database count is under the limit. They all move forward to the `DeployServerDatabaseService` and successfully create extra resources on the physical host.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Users are able to create more databases than they are supposed to, potentially also breaking the web interface.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: pterodactyl/panel&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The Pterodactyl Client API has a logic flaw that lets users bypass their assigned limits for database allocations. This happens because the database locking mechanism used in the controllers is totally broken and doesn&amp;#39;t actually lock anything.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Inside `DatabaseController.php`, the code tries to prevent multiple databases from being created at once by calling `$server-&amp;gt;databases()-&amp;gt;lockForUpdate()`. In Laravel, this just configures a query builder but never actually sends a command to the database because it’s missing a terminal method like `count()` or `get()`. It’s basically a no-op that does nothing.&lt;/p&gt;
&lt;p&gt;Since there’s no real lock, multiple requests hitting the endpoint at the exact same time will all see that the database count is under the limit. They all move forward to the `DeployServerDatabaseService` and successfully create extra resources on the physical host.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Users are able to create more databases than they are supposed to, potentially also breaking the web interface.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fgmm-w5cx-vrfw</guid>
    </item>
  </channel>
</rss>
