CVE-2026-25992
Case-Insensitive Path Bypass in SiYuan Allows Sensitive File Access
Publication date: 2026-02-10
Last updated on: 2026-02-23
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| b3log | siyuan | to 3.5.5 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in SiYuan, a personal knowledge management system, in versions prior to 3.5.5. The /api/file/getFile endpoint uses case-sensitive string equality checks to block access to sensitive files. However, on case-insensitive file systems like Windows, attackers can bypass these restrictions by using mixed-case paths, allowing them to read protected configuration files.
How can this vulnerability impact me? :
This vulnerability allows an attacker to bypass access controls and read sensitive configuration files that should be protected. This can lead to exposure of confidential information, potentially compromising the security of the system or the data it manages.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade SiYuan to version 3.5.5 or later, where the issue with case-sensitive string equality checks on the /api/file/getFile endpoint has been fixed.