<?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, 18 Oct 2026 09:39:31 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-267875</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-267875</link>
      <description>EUVD-2026-267875</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-267875</guid>
    </item>
    <item>
      <title>fkie_cve-2026-25992</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-25992</link>
      <description>&lt;p&gt;SiYuan is a personal knowledge management system. Prior to 3.5.5, the /api/file/getFile endpoint uses case-sensitive string equality checks to block access to sensitive files. On case-insensitive file systems such as Windows, attackers can bypass restrictions using mixed-case paths and read protected configuration files. This vulnerability is fixed in 3.5.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;SiYuan is a personal knowledge management system. Prior to 3.5.5, the /api/file/getFile endpoint uses case-sensitive string equality checks to block access to sensitive files. On case-insensitive file systems such as Windows, attackers can bypass restrictions using mixed-case paths and read protected configuration files. This vulnerability is fixed in 3.5.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-25992</guid>
    </item>
    <item>
      <title>GHSA-f72r-2h5j-7639 — SiYuan File Read API Case Sensitivity Bypass can Lead to Path Traversal</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f72r-2h5j-7639</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/siyuan-note/siyuan/kernel&lt;/p&gt;
&lt;p&gt;# File Read Interface Case Bypass Vulnerability
## Vulnerability Name
File Read Interface Case Bypass Vulnerability&lt;/p&gt;
&lt;p&gt;## Overview
The `/api/file/getFile` endpoint uses **case-sensitive string equality checks** to block access to sensitive files.
On case-insensitive file systems such as **Windows**, attackers can bypass restrictions using mixed-case paths
and read protected configuration files.&lt;/p&gt;
&lt;p&gt;## Impact
- Read sensitive information in configuration files (e.g., access codes, API Tokens, sync configurations, etc.).
- Remotely exploitable directly when the service is published without authentication.&lt;/p&gt;
&lt;p&gt;## Trigger Conditions
- Running on a **case-insensitive file system**.
- The caller can access `/api/file/getFile` (via CheckAuth or Token injection in published services).&lt;/p&gt;
&lt;p&gt;## PoC (Generic Example)
After enabling publication:&lt;/p&gt;
&lt;p&gt;**Request:**
```http
POST /api/file/getFile
Content-Type: application/json&lt;/p&gt;
&lt;p&gt;{&amp;#34;path&amp;#34;:&amp;#34;cOnf/conf.json&amp;#34;}
```&lt;/p&gt;
&lt;p&gt;**Expected Result:**
- Successfully return the content of the configuration file.&lt;/p&gt;
&lt;p&gt;## Root Cause
Path comparison uses strict case-sensitive string matching, without case normalization or identical file validation.&lt;/p&gt;
&lt;p&gt;## Fix Recommendations
- Normalize path casing before comparison (Windows/macOS).
- Use file-level comparison methods such as `os.SameFile`.
- Apply blacklist validation on sensitive paths **after case normalization**.&lt;/p&gt;
&lt;p&gt;## Notes
- Environment identifiers and sensitive information have been removed.&lt;/p&gt;
&lt;p&gt;## Solution Commit
`399a38893e8719968ea25…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/siyuan-note/siyuan/kernel&lt;/p&gt;
&lt;p&gt;# File Read Interface Case Bypass Vulnerability
## Vulnerability Name
File Read Interface Case Bypass Vulnerability&lt;/p&gt;
&lt;p&gt;## Overview
The `/api/file/getFile` endpoint uses **case-sensitive string equality checks** to block access to sensitive files.
On case-insensitive file systems such as **Windows**, attackers can bypass restrictions using mixed-case paths
and read protected configuration files.&lt;/p&gt;
&lt;p&gt;## Impact
- Read sensitive information in configuration files (e.g., access codes, API Tokens, sync configurations, etc.).
- Remotely exploitable directly when the service is published without authentication.&lt;/p&gt;
&lt;p&gt;## Trigger Conditions
- Running on a **case-insensitive file system**.
- The caller can access `/api/file/getFile` (via CheckAuth or Token injection in published services).&lt;/p&gt;
&lt;p&gt;## PoC (Generic Example)
After enabling publication:&lt;/p&gt;
&lt;p&gt;**Request:**
```http
POST /api/file/getFile
Content-Type: application/json&lt;/p&gt;
&lt;p&gt;{&amp;#34;path&amp;#34;:&amp;#34;cOnf/conf.json&amp;#34;}
```&lt;/p&gt;
&lt;p&gt;**Expected Result:**
- Successfully return the content of the configuration file.&lt;/p&gt;
&lt;p&gt;## Root Cause
Path comparison uses strict case-sensitive string matching, without case normalization or identical file validation.&lt;/p&gt;
&lt;p&gt;## Fix Recommendations
- Normalize path casing before comparison (Windows/macOS).
- Use file-level comparison methods such as `os.SameFile`.
- Apply blacklist validation on sensitive paths **after case normalization**.&lt;/p&gt;
&lt;p&gt;## Notes
- Environment identifiers and sensitive information have been removed.&lt;/p&gt;
&lt;p&gt;## Solution Commit
`399a38893e8719968ea25…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f72r-2h5j-7639</guid>
    </item>
  </channel>
</rss>
