<?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://vulnerability.circl.lu</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 05:57:12 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-52855</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-52855</link>
      <description>&lt;p&gt;Wings is the server control plane for Pterodactyl, a free, open-source game server management panel. Prior to 1.12.3, {{config.}} placeholders in egg configuration-file templates allow a low-privileged user to read {{config.token}}, {{config.token_id}}, and {{config.docker.registries}} from the full daemon configuration. This issue is fixed in version 1.12.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Wings is the server control plane for Pterodactyl, a free, open-source game server management panel. Prior to 1.12.3, {{config.}} placeholders in egg configuration-file templates allow a low-privileged user to read {{config.token}}, {{config.token_id}}, and {{config.docker.registries}} from the full daemon configuration. This issue is fixed in version 1.12.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-52855</guid>
    </item>
    <item>
      <title>GHSA-pfvc-3p5h-x7h6 — Wings exposes node configuration secrets through egg configuration-file templating</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-pfvc-3p5h-x7h6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/pterodactyl/wings&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;**Type:** Exposure of sensitive information / insufficiently protected credentials
leading to privilege escalation and full node compromise.&lt;/p&gt;
&lt;p&gt;Wings exposes its **entire** daemon configuration to the egg configuration-file
templating engine. When Wings renders a server&amp;#39;s configuration files, any
`{{config.&amp;lt;path&amp;gt;}}` placeholder in a replacement value is resolved against the
full marshalled daemon configuration, with no restriction on which paths may be
read.&lt;/p&gt;
&lt;p&gt;Because the Panel substitutes **user-controlled** egg variable values into these
replacements before sending them to Wings, a low-privileged user can smuggle a
`{{config.*}}` placeholder through a variable value. The placeholder is then
resolved by Wings and written into a file inside the user&amp;#39;s own server, where it
can be read via the file manager or SFTP.&lt;/p&gt;
&lt;p&gt;This allows reading, among other values:&lt;/p&gt;
&lt;p&gt;- `{{config.token}}` - the node&amp;#39;s daemon token, which is both the API bearer for
  the Panel⇆Wings channel **and** the HMAC signing key for every JWT the node
  issues;
- `{{config.token_id}}`;
- `{{config.docker.registries}}` - configured container-registry credentials.&lt;/p&gt;
&lt;p&gt;**Who is impacted:** Any deployment where a user who is not fully trusted can set
an egg variable value (e.g. a server owner or a subuser with the `startup.update`
permission) **and** the server&amp;#39;s egg renders a user-editable variable into a
configuration file via `{{server.build.env.*}}`. This pattern is common across
stock and community eggs, so…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/pterodactyl/wings&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;**Type:** Exposure of sensitive information / insufficiently protected credentials
leading to privilege escalation and full node compromise.&lt;/p&gt;
&lt;p&gt;Wings exposes its **entire** daemon configuration to the egg configuration-file
templating engine. When Wings renders a server&amp;#39;s configuration files, any
`{{config.&amp;lt;path&amp;gt;}}` placeholder in a replacement value is resolved against the
full marshalled daemon configuration, with no restriction on which paths may be
read.&lt;/p&gt;
&lt;p&gt;Because the Panel substitutes **user-controlled** egg variable values into these
replacements before sending them to Wings, a low-privileged user can smuggle a
`{{config.*}}` placeholder through a variable value. The placeholder is then
resolved by Wings and written into a file inside the user&amp;#39;s own server, where it
can be read via the file manager or SFTP.&lt;/p&gt;
&lt;p&gt;This allows reading, among other values:&lt;/p&gt;
&lt;p&gt;- `{{config.token}}` - the node&amp;#39;s daemon token, which is both the API bearer for
  the Panel⇆Wings channel **and** the HMAC signing key for every JWT the node
  issues;
- `{{config.token_id}}`;
- `{{config.docker.registries}}` - configured container-registry credentials.&lt;/p&gt;
&lt;p&gt;**Who is impacted:** Any deployment where a user who is not fully trusted can set
an egg variable value (e.g. a server owner or a subuser with the `startup.update`
permission) **and** the server&amp;#39;s egg renders a user-editable variable into a
configuration file via `{{server.build.env.*}}`. This pattern is common across
stock and community eggs, so…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-pfvc-3p5h-x7h6</guid>
    </item>
  </channel>
</rss>
