<?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>Wed, 07 Oct 2026 05:34:44 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-266054</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-266054</link>
      <description>EUVD-2026-266054</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-266054</guid>
    </item>
    <item>
      <title>fkie_cve-2026-23849</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-23849</link>
      <description>&lt;p&gt;File Browser provides a file managing interface within a specified directory and can be used to upload, delete, preview, rename, and edit files. Prior to version 2.55.0, the JSONAuth. Auth function contains a logic flaw that allows unauthenticated attackers to enumerate valid usernames by measuring the response time of the /api/login endpoint. The vulnerability exists due to a &amp;#34;short-circuit&amp;#34; evaluation in the authentication logic. When a username is not found in the database, the function returns immediately. However, if the username does exist, the code proceeds to verify the password using bcrypt (users.CheckPwd), which is a computationally expensive operation designed to be slow. This difference in execution path creates a measurable timing discrepancy. Version 2.55.0 contains a patch for the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;File Browser provides a file managing interface within a specified directory and can be used to upload, delete, preview, rename, and edit files. Prior to version 2.55.0, the JSONAuth. Auth function contains a logic flaw that allows unauthenticated attackers to enumerate valid usernames by measuring the response time of the /api/login endpoint. The vulnerability exists due to a &amp;#34;short-circuit&amp;#34; evaluation in the authentication logic. When a username is not found in the database, the function returns immediately. However, if the username does exist, the code proceeds to verify the password using bcrypt (users.CheckPwd), which is a computationally expensive operation designed to be slow. This difference in execution path creates a measurable timing discrepancy. Version 2.55.0 contains a patch for the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-23849</guid>
    </item>
    <item>
      <title>GHSA-43mm-m3h2-3prc — File Browser Vulnerable to Username Enumeration via Timing Attack in /api/login</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-43mm-m3h2-3prc</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/filebrowser/filebrowser, Go: github.com/filebrowser/filebrowser/v2&lt;/p&gt;
&lt;p&gt;### Summary
The JSONAuth.Auth function contains a logic flaw that allows unauthenticated attackers to enumerate valid usernames by measuring the response time of the /api/login endpoint.&lt;/p&gt;
&lt;p&gt;### Details
The vulnerability exists due to a &amp;#34;short-circuit&amp;#34; evaluation in the authentication logic. When a username is not found in the database, the function returns immediately. However, if the username does exist, the code proceeds to verify the password using bcrypt (users.CheckPwd), which is a computationally expensive operation designed to be slow.&lt;/p&gt;
&lt;p&gt;This difference in execution path creates a measurable timing discrepancy:&lt;/p&gt;
&lt;p&gt;Invalid User: ~1ms execution (Database lookup only).
Valid User: ~50ms+ execution (Database lookup + Bcrypt hashing).&lt;/p&gt;
&lt;p&gt;In auth/json.go:
```go
// auth/json.go line 54
u, err := usr.Get(srv.Root, cred.Username)
// VULNERABILITY:
// If &amp;#39;err != nil&amp;#39; (User not found), the OR condition short-circuits.
// The second part (!users.CheckPwd) is NEVER executed.
//
// If &amp;#39;err == nil&amp;#39; (User found), the code MUST execute users.CheckPwd (Bcrypt).
if err != nil || !users.CheckPwd(cred.Password, u.Password) {
    return nil, os.ErrPermission
}
```
### PoC
The following Python script automates the attack. It first calibrates the network latency using random (non-existent) users to establish a baseline/threshold, and then tests a list of target usernames. Valid users are detected when the response time exceeds the calculated threshold.&lt;/p&gt;
&lt;p&gt;```python
import requests
import time
import…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/filebrowser/filebrowser, Go: github.com/filebrowser/filebrowser/v2&lt;/p&gt;
&lt;p&gt;### Summary
The JSONAuth.Auth function contains a logic flaw that allows unauthenticated attackers to enumerate valid usernames by measuring the response time of the /api/login endpoint.&lt;/p&gt;
&lt;p&gt;### Details
The vulnerability exists due to a &amp;#34;short-circuit&amp;#34; evaluation in the authentication logic. When a username is not found in the database, the function returns immediately. However, if the username does exist, the code proceeds to verify the password using bcrypt (users.CheckPwd), which is a computationally expensive operation designed to be slow.&lt;/p&gt;
&lt;p&gt;This difference in execution path creates a measurable timing discrepancy:&lt;/p&gt;
&lt;p&gt;Invalid User: ~1ms execution (Database lookup only).
Valid User: ~50ms+ execution (Database lookup + Bcrypt hashing).&lt;/p&gt;
&lt;p&gt;In auth/json.go:
```go
// auth/json.go line 54
u, err := usr.Get(srv.Root, cred.Username)
// VULNERABILITY:
// If &amp;#39;err != nil&amp;#39; (User not found), the OR condition short-circuits.
// The second part (!users.CheckPwd) is NEVER executed.
//
// If &amp;#39;err == nil&amp;#39; (User found), the code MUST execute users.CheckPwd (Bcrypt).
if err != nil || !users.CheckPwd(cred.Password, u.Password) {
    return nil, os.ErrPermission
}
```
### PoC
The following Python script automates the attack. It first calibrates the network latency using random (non-existent) users to establish a baseline/threshold, and then tests a list of target usernames. Valid users are detected when the response time exceeds the calculated threshold.&lt;/p&gt;
&lt;p&gt;```python
import requests
import time
import…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-43mm-m3h2-3prc</guid>
    </item>
  </channel>
</rss>
