SiYuan File Read API Case Sensitivity Bypass can Lead to Path Traversal

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-25992: 0.59% estimated exploitation activity in the next 30 days; percentile 48.12 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

File Read Interface Case Bypass Vulnerability Vulnerability Name File Read Interface Case Bypass Vulnerability 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. 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. Trigger Conditions - Running on a case-insensitive file system. - The caller can access /api/file/getFile (via CheckAuth or Token injection in published services). PoC (Generic Example) After enabling publication: Request: Expected Result: - Successfully return the content of the configuration file. Root Cause Path comparison uses strict case-sensitive string matching, without case normalization or identical…

Published by the source

28 Jan 2026, 23:00 UTC

Last modified by the source

10 Feb 2026, 19:56 UTC

Source last checked

26 Oct 2026, 15:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f72r-2h5j-7639

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-25992

Advisory: SiYuan File Read API Case Sensitivity Bypass can Lead to Path Traversal
IDs: CVE-2026-25992, GHSA-f72r-2h5j-7639
Record: https://patchnext.com/advisories/cve-2026-25992 (revision 1, source checked 26 Oct 2026, 15:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected <= 0.0.0-20260126094835-d5d10dd41b0c

## Suggested inspection (read-only)
- Go github.com/siyuan-note/siyuan/kernel: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/siyuan-note/siyuan/kernel.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-f72r-2h5j-7639 (GitHub-reviewed advisory GHSA-f72r-2h5j-7639 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <=0.0.0-20260126094835-d5d10dd41b0c)

Commands are suggestions: review each one before running it.