dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-54066

HIGH · 7.5 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SiYuan is an open-source personal knowledge management system. Prior to 3.7.0, the patch for CVE-2026-41894 ("Path Traversal via Double URL Encoding") sanitized the /export/ route but the identical root cause remains in the /assets/*path route. In publish mode (anonymous read-only HTTP endpoint, default port 6808), an unauthenticated remote attacker can read arbitrary files inside WorkspaceDir — including conf/conf.json (which contains the AccessAuthCode SHA256 hash, API token, and sync keys), temp/siyuan.db, temp/blocktree.db, and siyuan.log — by double-URL-encoding .. segments. This vulnerability is fixed in 3.7.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Path traversal vulnerability in SiYuan's /assets/*path route allows unauthenticated remote attackers in publish mode to read arbitrary files via double-URL-encoded '../' sequences, exposing sensitive configuration (conf/conf.json containing AccessAuthCode, API tokens, sync keys), databases, and log files.

MitigationUpgrade to SiYuan 3.7.0 or later; if immediate upgrade is not possible, disable publish mode or restrict network access to port 6808.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SiYuan installation and version
    Locate the SiYuan application and identify its version number (typically found in the application metadata, about dialog, or installation directory)
    Affected if The installed version is earlier than 3.7.0 (the patched version)
  2. Check if publish mode is enabled
    Examine the SiYuan configuration files or settings panel to determine whether publish mode is currently active
    Affected if Publish mode is enabled and the server is network-accessible
  3. Verify network exposure of the application
    Check if the SiYuan server (typically listening on port 6806 or 6808) is exposed to untrusted networks or the internet
    Affected if The application is accessible from untrusted network locations
  4. Test the vulnerable endpoint
    Send a request to /assets/ with a double-URL-encoded path traversal sequence (for example, encode ../ as %252e%252e%252f) to see if arbitrary file读取 is possible
    Affected if The server returns file contents from paths outside the intended assets directory

You are affected if SiYuan version is below 3.7.0 AND publish mode is enabled AND the server is network-accessible, allowing an unauthenticated attacker to exploit the path traversal in the /assets/*path route.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to SiYuan 3.7.0 or later; if immediate upgrade is not possible, disable publish mode or restrict network access to port 6808.

Recommended fix High confidence

3.7.0

  1. Upgrade SiYuan to version 3.7.0 or later to resolve the path traversal vulnerability
  2. If using publish mode (anonymous read-only HTTP endpoint on port 6808), ensure the upgrade is applied to the server running this service
  3. After upgrading, verify that the /assets/*path route no longer accepts double-encoded path traversal sequences
  4. Confirm that sensitive files (conf/conf.json, temp/siyuan.db, temp/blocktree.db, siyuan.log) are no longer accessible via the vulnerability

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54066 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-54066 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data