<?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>Sun, 22 Nov 2026 20:39:44 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-409024</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-409024</link>
      <description>EUVD-2026-409024</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-409024</guid>
    </item>
    <item>
      <title>fkie_cve-2026-69131</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-69131</link>
      <description>&lt;p&gt;django-filer is a file and image management application for Django. Prior to 3.5.0, the delete_files_or_folders action in filer/admin/folderadmin.py checks global Django model-level deletion permission but omits check_folder_edit_permissions and check_files_edit_permissions when FILER_ENABLE_PERMISSIONS is enabled. An authenticated staff user who has a global delete_file, delete_folder, or delete_image permission but is limited to read-only access by FolderPermission can therefore delete files, folders, and descendants from the restricted folder. Deployments using the default disabled per-folder permission system are not affected, and the issue does not create a read-confidentiality impact. This issue is fixed in version 3.5.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;django-filer is a file and image management application for Django. Prior to 3.5.0, the delete_files_or_folders action in filer/admin/folderadmin.py checks global Django model-level deletion permission but omits check_folder_edit_permissions and check_files_edit_permissions when FILER_ENABLE_PERMISSIONS is enabled. An authenticated staff user who has a global delete_file, delete_folder, or delete_image permission but is limited to read-only access by FolderPermission can therefore delete files, folders, and descendants from the restricted folder. Deployments using the default disabled per-folder permission system are not affected, and the issue does not create a read-confidentiality impact. This issue is fixed in version 3.5.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-69131</guid>
    </item>
    <item>
      <title>GHSA-vf85-8ff2-3r9w — django-filer: Missing per-object authorization on `discard` and `edit_redirect` version transitions</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vf85-8ff2-3r9w</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: django-filer&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;When django-filer&amp;#39;s optional per-folder permission system is enabled (`FILER_ENABLE_PERMISSIONS=True`), the &amp;#34;Delete files and/or folders&amp;#34; admin action does **not** enforce per-folder edit permissions the way every other mutating action does. A staff user who is scoped **read-only** on a folder via `FolderPermission` (`can_edit = DENY`), but who holds the global Django model-level `delete_*` permission, can delete files and entire subfolders inside that folder — even though their move, rename, copy, and resize actions on the same folder are correctly denied.&lt;/p&gt;
&lt;p&gt;This is an integrity / edit-control gap (unauthorized deletion). It is **not** a read-confidentiality issue: filer files are world-downloadable by design, so no confidentiality claim is made.&lt;/p&gt;
&lt;p&gt;## Affected versions&lt;/p&gt;
&lt;p&gt;- django-filer `&amp;lt;= 3.4.4` (verified end-to-end on 3.4.4 and on `master` prior to   the fix).&lt;/p&gt;
&lt;p&gt;Only installations running with `FILER_ENABLE_PERMISSIONS = True` (the optional per-folder `FolderPermission` system) are affected. Deployments that leave permissions disabled (the default) rely solely on Django model-level permissions and are not impacted by this specific gap.&lt;/p&gt;
&lt;p&gt;## Patched versions&lt;/p&gt;
&lt;p&gt;- Fixed in PR [#1605](https://github.com/django-cms/django-filer/pull/1605).   Upgrade to the first release containing that commit (`3.5.0` or later).&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The `delete_files_or_folders` admin action in `filer/admin/folderadmin.py` authorized deletion using only:&lt;/p&gt;
&lt;p&gt;1. `self.has_delete_permission(request)`…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: django-filer&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;When django-filer&amp;#39;s optional per-folder permission system is enabled (`FILER_ENABLE_PERMISSIONS=True`), the &amp;#34;Delete files and/or folders&amp;#34; admin action does **not** enforce per-folder edit permissions the way every other mutating action does. A staff user who is scoped **read-only** on a folder via `FolderPermission` (`can_edit = DENY`), but who holds the global Django model-level `delete_*` permission, can delete files and entire subfolders inside that folder — even though their move, rename, copy, and resize actions on the same folder are correctly denied.&lt;/p&gt;
&lt;p&gt;This is an integrity / edit-control gap (unauthorized deletion). It is **not** a read-confidentiality issue: filer files are world-downloadable by design, so no confidentiality claim is made.&lt;/p&gt;
&lt;p&gt;## Affected versions&lt;/p&gt;
&lt;p&gt;- django-filer `&amp;lt;= 3.4.4` (verified end-to-end on 3.4.4 and on `master` prior to   the fix).&lt;/p&gt;
&lt;p&gt;Only installations running with `FILER_ENABLE_PERMISSIONS = True` (the optional per-folder `FolderPermission` system) are affected. Deployments that leave permissions disabled (the default) rely solely on Django model-level permissions and are not impacted by this specific gap.&lt;/p&gt;
&lt;p&gt;## Patched versions&lt;/p&gt;
&lt;p&gt;- Fixed in PR [#1605](https://github.com/django-cms/django-filer/pull/1605).   Upgrade to the first release containing that commit (`3.5.0` or later).&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The `delete_files_or_folders` admin action in `filer/admin/folderadmin.py` authorized deletion using only:&lt;/p&gt;
&lt;p&gt;1. `self.has_delete_permission(request)`…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vf85-8ff2-3r9w</guid>
    </item>
  </channel>
</rss>
