dbcve.org
CWE-346Weakness · CWE-346

CVE-2026-54069

CRITICAL · 9.2 CVSS v4.0 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 →
100/100
Remediation priority · Urgent
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 an open-source personal knowledge management system. Prior to 3.7.0, SiYuan Note's kernel HTTP server unconditionally trusts all chrome-extension:// origins, granting RoleAdministrator access to every installed browser extension without any authentication. Combined with the default empty AccessAuthCode on desktop installs, any Chrome/Chromium extension -- including a compromised legitimate extension via supply chain attack -- can make fully authenticated admin API calls to the SiYuan kernel at 127.0.0.1:6806, enabling data exfiltration, stored XSS injection, and configuration tampering. 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

SiYuan Note's kernel HTTP server unconditionally trusts all chrome-extension:// origins, granting RoleAdministrator access to every installed browser extension without any authentication. Combined with the default empty AccessAuthCode on desktop installs, any Chrome/Chromium extension can make fully authenticated admin API calls to 127.0.0.1:6806.

MitigationUpgrade to SiYuan version 3.7.0 or later. Additionally, ensure AccessAuthCode is configured even on desktop installs to enforce proper authentication.

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
High
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Verify SiYuan Note is installed and running
    Check for the SiYuan Note process or look for its data directory (typically at ~/Documents/SiYuan or in AppData/Application Support depending on OS). Also verify port 6806 is listening via 'netstat -an | grep 6806' or 'ss -tlnp | grep 6806'.
    Affected if SiYuan Note is running with its HTTP server listening on port 6806.
  2. Determine installed SiYuan version
    Open SiYuan Note and navigate to Settings > About, or inspect the version file in the SiYuan data directory. Compare the version number to 3.7.0.
    Affected if The installed version is earlier than 3.7.0.
  3. Check AccessAuthCode configuration
    Inspect the SiYuan configuration file (typically workspace/config.json or conf/conf.json in the data directory) for the 'accessAuthCode' field. On command line, search for this field: 'grep -r "accessAuthCode" /path/to/siyuan/data/' or on Windows search the config files.
    Affected if The accessAuthCode field is empty, missing, or set to a default/blank value.
  4. Confirm HTTP server accepts localhost connections
    Attempt a curl request to the local API: 'curl -s http://127.0.0.1:6806/api/system/version' or check if the endpoint responds without providing any auth token.
    Affected if The server responds to requests on 127.0.0.1:6806 without requiring authentication.

A user is affected if SiYuan Note version is below 3.7.0, the HTTP server is accessible on localhost port 6806, and no AccessAuthCode is configured, allowing any browser extension to make admin API calls.

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 version 3.7.0 or later. Additionally, ensure AccessAuthCode is configured even on desktop installs to enforce proper authentication.

Recommended fix High confidence

3.7.0

  1. 1. Check current SiYuan version by navigating to Settings > About > Version
  2. 2. Backup all SiYuan data by exporting the workspace to a safe location
  3. 3. Download SiYuan version 3.7.0 or later from the official GitHub releases page (https://github.com/siyuan-note/siyuan/releases)
  4. 4. Install the new version by running the downloaded installer
  5. 5. After upgrade, verify the version shows 3.7.0 or higher in Settings > About > Version
  6. 6. As an additional security measure, set a non-empty AccessAuthCode in Settings > Security to protect the local API even if the origin validation is bypassed in the future
Caveat Review release notes for 3.7.0 to check for any breaking changes in plugins or data format

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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