<?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 11:20:32 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-276803</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-276803</link>
      <description>EUVD-2026-276803</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-276803</guid>
    </item>
    <item>
      <title>fkie_cve-2026-32761</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-32761</link>
      <description>&lt;p&gt;File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. Versions 2.61.0 and below contain a permission enforcement bypass which allows users who are denied download privileges (perm.download = false) but granted share privileges (perm.share = true) to exfiltrate file content by creating public share links. While the direct raw download endpoint (/api/raw/) correctly enforces the download permission, the share creation endpoint only checks Perm.Share, and the public download handler (/api/public/dl/&amp;lt;hash&amp;gt;) serves file content without verifying that the original file owner has download permission. This means any authenticated user with share access can circumvent download restrictions by sharing a file and then retrieving it via the unauthenticated public download URL. The vulnerability undermines data-loss prevention and role-separation policies, as restricted users can publicly distribute files they are explicitly blocked from downloading directly. This issue has been fixed in version 2.62.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. Versions 2.61.0 and below contain a permission enforcement bypass which allows users who are denied download privileges (perm.download = false) but granted share privileges (perm.share = true) to exfiltrate file content by creating public share links. While the direct raw download endpoint (/api/raw/) correctly enforces the download permission, the share creation endpoint only checks Perm.Share, and the public download handler (/api/public/dl/&amp;lt;hash&amp;gt;) serves file content without verifying that the original file owner has download permission. This means any authenticated user with share access can circumvent download restrictions by sharing a file and then retrieving it via the unauthenticated public download URL. The vulnerability undermines data-loss prevention and role-separation policies, as restricted users can publicly distribute files they are explicitly blocked from downloading directly. This issue has been fixed in version 2.62.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-32761</guid>
    </item>
    <item>
      <title>GHSA-68j5-4m99-w9w9 — File Browser has an Authorization Policy Bypass in Public Share Download Flow</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-68j5-4m99-w9w9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: https://github.com/filebrowser/filebrowser&lt;/p&gt;
&lt;p&gt;### Summary
A permission enforcement flaw allows users without download privileges (`download=false`) to still expose and retrieve file content via public share links when they retain share privileges (`share=true`). This bypasses intended access control policy and enables unauthorized data exfiltration to unauthenticated users. Where download restrictions are used for data-loss prevention or role separation.&lt;/p&gt;
&lt;p&gt;### Details
The backend applies inconsistent authorization checks across download paths:&lt;/p&gt;
&lt;p&gt;- Direct raw download correctly enforces `Perm.Download`:
  - [[raw.go](https://github.com/filebrowser/filebrowser/blob/master/http/raw.go#82)](filebrowser/http/raw.go:82)
- Share creation only enforces `Perm.Share`:
  - [[share.go](https://github.com/filebrowser/filebrowser/blob/master/http/share.go#21)](filebrowser/http/share.go:21)
- Public share/download handlers serve shared content without verifying owner `Perm.Download`:
  - [public.go](https://github.com/filebrowser/filebrowser/blob/master/http/public.go#18)(filebrowser/http/public.go:18)
  - [public.go](https://github.com/filebrowser/filebrowser/blob/master/http/public.go#116)(filebrowser/http/public.go:116)&lt;/p&gt;
&lt;p&gt;As a result, a user who is blocked from direct downloads can create a share and obtain the same file via `/api/public/dl/&amp;lt;hash&amp;gt;`.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;1. Create a non-admin user with:
- `perm.share = true`
- `perm.download = false`&lt;/p&gt;
&lt;p&gt;2. Login as that user and upload a **PDF** file:
- `POST /api/resources/nodl_secret_&amp;lt;rand&amp;gt;.pdf`…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: https://github.com/filebrowser/filebrowser&lt;/p&gt;
&lt;p&gt;### Summary
A permission enforcement flaw allows users without download privileges (`download=false`) to still expose and retrieve file content via public share links when they retain share privileges (`share=true`). This bypasses intended access control policy and enables unauthorized data exfiltration to unauthenticated users. Where download restrictions are used for data-loss prevention or role separation.&lt;/p&gt;
&lt;p&gt;### Details
The backend applies inconsistent authorization checks across download paths:&lt;/p&gt;
&lt;p&gt;- Direct raw download correctly enforces `Perm.Download`:
  - [[raw.go](https://github.com/filebrowser/filebrowser/blob/master/http/raw.go#82)](filebrowser/http/raw.go:82)
- Share creation only enforces `Perm.Share`:
  - [[share.go](https://github.com/filebrowser/filebrowser/blob/master/http/share.go#21)](filebrowser/http/share.go:21)
- Public share/download handlers serve shared content without verifying owner `Perm.Download`:
  - [public.go](https://github.com/filebrowser/filebrowser/blob/master/http/public.go#18)(filebrowser/http/public.go:18)
  - [public.go](https://github.com/filebrowser/filebrowser/blob/master/http/public.go#116)(filebrowser/http/public.go:116)&lt;/p&gt;
&lt;p&gt;As a result, a user who is blocked from direct downloads can create a share and obtain the same file via `/api/public/dl/&amp;lt;hash&amp;gt;`.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;1. Create a non-admin user with:
- `perm.share = true`
- `perm.download = false`&lt;/p&gt;
&lt;p&gt;2. Login as that user and upload a **PDF** file:
- `POST /api/resources/nodl_secret_&amp;lt;rand&amp;gt;.pdf`…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-68j5-4m99-w9w9</guid>
    </item>
  </channel>
</rss>
