https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-15T11:20:33.029034+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-276803 EUVD-2026-276803 2026-10-15T11:20:33.031269+00:00 EUVD-2026-276803 https://cve.radiocsirt.org/vuln/fkie_cve-2026-32761 fkie_cve-2026-32761 2026-10-15T11:20:33.031298+00:00

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/<hash>) 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.

 https://cve.radiocsirt.org/vuln/ghsa-68j5-4m99-w9w9 GHSA-68j5-4m99-w9w9 — File Browser has an Authorization Policy Bypass in Public Share Download Flow 2026-10-15T11:20:33.031335+00:00

Affected: Go: https://github.com/filebrowser/filebrowser

### 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.

### Details The backend applies inconsistent authorization checks across download paths:

- 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)

As a result, a user who is blocked from direct downloads can create a share and obtain the same file via `/api/public/dl/<hash>`.

### PoC

1. Create a non-admin user with: - `perm.share = true` - `perm.download = false`

2. Login as that user and upload a **PDF** file: - `POST /api/resources/nodl_secret_<rand>.pdf`…