<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-20T16:35:53.141585+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-338108</id>
    <title>EUVD-2026-338108</title>
    <updated>2026-11-20T16:35:53.143783+00:00</updated>
    <content>EUVD-2026-338108</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-338108"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-62683</id>
    <title>fkie_cve-2026-62683</title>
    <updated>2026-11-20T16:35:53.143813+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. Prior to 2.63.17, File Browser can leave a public directory share behind when the shared directory is deleted through a path with a trailing slash because the share cleanup path calls DeleteWithPathPrefix(file.Path, userID) and the Bolt backend performs the database prefix query with the unnormalized path before trimming the slash for boundary checks, so deleting /a/ does not delete the stored /a share and the stale public share exposes future content if the same path is recreated. This issue is fixed in version 2.63.17.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-62683"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-pp88-jhwj-5qh5</id>
    <title>GHSA-pp88-jhwj-5qh5 — File Browser: Trailing-slash directory deletion leaves public shares active for recreated paths</title>
    <updated>2026-11-20T16:35:53.143845+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/filebrowser/filebrowser/v2</p>
<p>## Summary</p>
<p>File Browser v2.63.15 can leave a public directory share behind when the shared directory is deleted through a path with a trailing slash. The share cleanup path calls `DeleteWithPathPrefix(file.Path, userID)`, but the Bolt backend performs the database prefix query with the unnormalized argument before trimming the slash for boundary checks. For a stored share at `/a`, deleting `/a/` queries for paths prefixed by `/a/`, so the exact `/a` share is never loaded and never deleted.</p>
<p>If a directory with the same path is later recreated, the stale public share becomes active again and exposes the new directory contents through the old public URL.</p>
<p>## Impact</p>
<p>An authenticated user with share, download, and delete permissions can create a valid public share, delete the shared path with a trailing slash, and leave the public link in storage. The link is dormant while the path does not exist, but it exposes future content if the same path is recreated later. The final data exposure is unauthenticated through the public share URL.</p>
<p>This bypasses the intended lifecycle cleanup around public shares and is adjacent to the recent public-share path-existence and prefix-boundary fixes.</p>
<p>## Reproduction</p>
<p>The following test was run against v2.63.15, commit `be23ab3a15bf957928ecfed88de5ab67850c1b9c`.</p>
<p>1. Create a scoped user with share, download, and delete permissions.
2. Create `/a/old.txt` in that user's scope.
3. Store a valid public share row with `Hash: "h"`, `UserID: 1`, and…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-pp88-jhwj-5qh5"/>
  </entry>
</feed>
