dbcve.org
SiyuanApplication · B3log

CVE-2026-30869

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 3.5.10 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 a personal knowledge management system. Prior to 3.5.10, a path traversal vulnerability in the /export endpoint allows an attacker to read arbitrary files from the server filesystem. By exploiting double‑encoded traversal sequences, an attacker can access sensitive files such as conf/conf.json, which contains secrets including the API token, cookie signing key, and workspace access authentication code. Leaking these secrets may enable administrative access to the SiYuan kernel API, and in certain deployment scenarios could potentially be chained into remote code execution (RCE). This vulnerability is fixed in 3.5.10.

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

A path traversal vulnerability in SiYuan's /export endpoint allows reading arbitrary files via double-encoded traversal sequences. The attack can access conf/conf.json containing API tokens, cookie signing keys, and workspace authentication codes, enabling administrative API access and potential RCE in certain deployments.

MitigationUpgrade to SiYuan version 3.5.10 or later. Review access logs for exploitation attempts, and rotate any leaked credentials (API tokens, signing keys, authentication codes) immediately.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SiyuanApplication
Affected:< 3.5.10

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
High
Availability
High

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

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. Identify installed Siyuan version
    Locate the Siyuan installation and check its version number. In typical deployments, this can be found in the application UI under Help > About, or in installation directory metadata. Compare the version against the affected range: versions prior to 3.5.10 are vulnerable.
    Affected if The installed version is lower than 3.5.10
  2. Confirm /export endpoint exposure
    Determine if the Siyuan web interface is exposed to the network. Check firewall rules, reverse proxy configuration, or cloud security groups for any allow rules that permit external access to port 6806 (the default Siyuan port) or the /export API endpoint.
    Affected if The /export endpoint is accessible from untrusted networks or the internet
  3. Review access logs for exploitation indicators
    Examine Siyuan access logs (typically found in the workspace directory under temp/access.log or similar) for requests containing double-encoded traversal patterns such as %252e%252e%252f (encoded ../) targeting the /export endpoint.
    Affected if Logs contain requests with double-encoded path traversal sequences to /export, especially attempts to access conf/ or conf.json
  4. Check for credential exposure in logs
    After identifying potential exploitation attempts, review logs for any successful access patterns that may indicate the conf/conf.json file was successfully retrieved.
    Affected if Logs show successful responses to traversal attempts reaching configuration files in the conf directory

A system is affected if it runs Siyuan version lower than 3.5.10 AND has the /export endpoint network-accessible, with confirmation via version check or log evidence of traversal attempts.

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
Upgrade available Upgrade to 3.5.10 or later
Fixed in 3.5.10
Interim mitigation

Upgrade to SiYuan version 3.5.10 or later. Review access logs for exploitation attempts, and rotate any leaked credentials (API tokens, signing keys, authentication codes) immediately.

Recommended fix High confidence

3.5.10

  1. 1. Back up the current Siyuan installation and workspace data.
  2. 2. Download Siyuan version 3.5.10 or later from the official source (https://github.com/siyuan-note/siyuan/releases).
  3. 3. Stop the running Siyuan instance.
  4. 4. Upgrade the Siyuan installation to version 3.5.10.
  5. 5. Start the upgraded Siyuan instance.
  6. 6. Verify the /export endpoint no longer accepts double-encoded traversal sequences.
  7. 7. Rotate any credentials that may have been exposed, as a precaution.

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

Fix this in Siyuan Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30869 — 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-30869 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