<?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 12:49:35 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-210510</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-210510</link>
      <description>EUVD-2026-210510</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-210510</guid>
    </item>
    <item>
      <title>fkie_cve-2023-32321</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-32321</link>
      <description>&lt;p&gt;CKAN is an open-source data management system for powering data hubs and data portals. Multiple vulnerabilities have been discovered in Ckan which may lead to remote code execution. An arbitrary file write in `resource_create` and `package_update` actions, using the `ResourceUploader` object.  Also reachable via `package_create`, `package_revise`, and `package_patch` via calls to `package_update`. Remote code execution via unsafe pickle loading, via Beaker&amp;#39;s session store when configured to use the file session store backend. Potential DOS due to lack of a length check on the resource id. Information disclosure: A user with permission to create a resource can access any other resource on the system if they know the id, even if they don&amp;#39;t have access to it. Resource overwrite: A user with permission to create a resource can overwrite any resource if they know the id, even if they don&amp;#39;t have access to it. A user with permissions to create or edit a dataset can upload a resource with a specially crafted id to write the uploaded file in an arbitrary location. This can be leveraged to Remote Code Execution via Beaker&amp;#39;s insecure pickle loading. All the above listed vulnerabilities have been fixed in CKAN 2.9.9 and CKAN 2.10.1. Users are advised to upgrade. There are no known workarounds for these issues.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;CKAN is an open-source data management system for powering data hubs and data portals. Multiple vulnerabilities have been discovered in Ckan which may lead to remote code execution. An arbitrary file write in `resource_create` and `package_update` actions, using the `ResourceUploader` object.  Also reachable via `package_create`, `package_revise`, and `package_patch` via calls to `package_update`. Remote code execution via unsafe pickle loading, via Beaker&amp;#39;s session store when configured to use the file session store backend. Potential DOS due to lack of a length check on the resource id. Information disclosure: A user with permission to create a resource can access any other resource on the system if they know the id, even if they don&amp;#39;t have access to it. Resource overwrite: A user with permission to create a resource can overwrite any resource if they know the id, even if they don&amp;#39;t have access to it. A user with permissions to create or edit a dataset can upload a resource with a specially crafted id to write the uploaded file in an arbitrary location. This can be leveraged to Remote Code Execution via Beaker&amp;#39;s insecure pickle loading. All the above listed vulnerabilities have been fixed in CKAN 2.9.9 and CKAN 2.10.1. Users are advised to upgrade. There are no known workarounds for these issues.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-32321</guid>
    </item>
    <item>
      <title>GHSA-446m-hmmm-hm8m — Ckan remote code execution and private information access via crafted resource ids</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-446m-hmmm-hm8m</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: ckan&lt;/p&gt;
&lt;p&gt;Specific vulnerabilities:&lt;/p&gt;
&lt;p&gt;* Arbitrary file write in `resource_create` and `package_update` actions, using the `ResourceUploader` object.  Also reachable via `package_create`, `package_revise`, and `package_patch` via calls to `package_update`.
* Remote code execution via unsafe pickle loading, via Beaker&amp;#39;s session store when configured to use the file session store backend.
* Potential DOS due to lack of a length check on the resource id.
* Information disclosure: A user with permission to create a resource can access any other resource on the system if they know the id, even if they don&amp;#39;t have access to it.
* Resource overwrite: A user with permission to create a resource can overwrite any resource if they know the id, even if they don&amp;#39;t have access to it.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A user with permissions to create or edit a dataset can upload a resource with a specially crafted id to write the uploaded file in an arbitrary location. This can be leveraged to Remote Code Execution via Beaker&amp;#39;s insecure pickle loading.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;All the above listed vulnerabilities have been fixed in CKAN 2.9.9 and CKAN 2.10.1
The patches for CKAN 2.9 should apply easily to previous CKAN versions.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: ckan&lt;/p&gt;
&lt;p&gt;Specific vulnerabilities:&lt;/p&gt;
&lt;p&gt;* Arbitrary file write in `resource_create` and `package_update` actions, using the `ResourceUploader` object.  Also reachable via `package_create`, `package_revise`, and `package_patch` via calls to `package_update`.
* Remote code execution via unsafe pickle loading, via Beaker&amp;#39;s session store when configured to use the file session store backend.
* Potential DOS due to lack of a length check on the resource id.
* Information disclosure: A user with permission to create a resource can access any other resource on the system if they know the id, even if they don&amp;#39;t have access to it.
* Resource overwrite: A user with permission to create a resource can overwrite any resource if they know the id, even if they don&amp;#39;t have access to it.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A user with permissions to create or edit a dataset can upload a resource with a specially crafted id to write the uploaded file in an arbitrary location. This can be leveraged to Remote Code Execution via Beaker&amp;#39;s insecure pickle loading.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;All the above listed vulnerabilities have been fixed in CKAN 2.9.9 and CKAN 2.10.1
The patches for CKAN 2.9 should apply easily to previous CKAN versions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-446m-hmmm-hm8m</guid>
    </item>
    <item>
      <title>gsd-2023-32321</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-32321</link>
      <description>gsd-2023-32321</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-32321</guid>
    </item>
    <item>
      <title>PYSEC-2026-312 — Ckan remote code execution and private information access via crafted resource ids</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-312</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: ckan&lt;/p&gt;
&lt;p&gt;Specific vulnerabilities:&lt;/p&gt;
&lt;p&gt;* Arbitrary file write in `resource_create` and `package_update` actions, using the `ResourceUploader` object.  Also reachable via `package_create`, `package_revise`, and `package_patch` via calls to `package_update`.
 * Remote code execution via unsafe pickle loading, via Beaker&amp;#39;s session store when configured to use the file session store backend.
* Potential DOS due to lack of a length check on the resource id.
* Information disclosure: A user with permission to create a resource can access any other resource on the system if they know the id, even if they don&amp;#39;t have access to it.
* Resource overwrite: A user with permission to create a resource can overwrite any resource if they know the id, even if they don&amp;#39;t have access to it.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A user with permissions to create or edit a dataset can upload a resource with a specially crafted id to write the uploaded file in an arbitrary location. This can be leveraged to Remote Code Execution via Beaker&amp;#39;s insecure pickle loading.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;All the above listed vulnerabilities have been fixed in CKAN 2.9.9 and CKAN 2.10.1
The patches for CKAN 2.9 should apply easily to previous CKAN versions.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: ckan&lt;/p&gt;
&lt;p&gt;Specific vulnerabilities:&lt;/p&gt;
&lt;p&gt;* Arbitrary file write in `resource_create` and `package_update` actions, using the `ResourceUploader` object.  Also reachable via `package_create`, `package_revise`, and `package_patch` via calls to `package_update`.
 * Remote code execution via unsafe pickle loading, via Beaker&amp;#39;s session store when configured to use the file session store backend.
* Potential DOS due to lack of a length check on the resource id.
* Information disclosure: A user with permission to create a resource can access any other resource on the system if they know the id, even if they don&amp;#39;t have access to it.
* Resource overwrite: A user with permission to create a resource can overwrite any resource if they know the id, even if they don&amp;#39;t have access to it.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A user with permissions to create or edit a dataset can upload a resource with a specially crafted id to write the uploaded file in an arbitrary location. This can be leveraged to Remote Code Execution via Beaker&amp;#39;s insecure pickle loading.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;All the above listed vulnerabilities have been fixed in CKAN 2.9.9 and CKAN 2.10.1
The patches for CKAN 2.9 should apply easily to previous CKAN versions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-312</guid>
    </item>
  </channel>
</rss>
