Skip to main content
Menu
CVEs

CVE

SiYuan credential file disclosure in getFile API

Affects SiYuan before 3.8.9 when a publish-enabled widget containing a regular credentials.json file is referenced by a publish-allowed document. Fixed in 3.8.9.

CVE-2026-126264EUVD-2026-125257GHSA-3PM7-CC76-7J2PGHSA-CCPQ-6VHP-2MRJPublished Updated Summary written by a model

8.3HighCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 3.8.9
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. The widget must be referenced by a publish-allowed document. The widget must be installed and publish-enabled, and contain a regular file named credentials.json.

Summary

SiYuan before 3.8.9 contains an information disclosure vulnerability that allows authenticated Reader users to retrieve credential-named widget files by bypassing the sensitive-path guard in getFile. Attackers can request paths like /data/widgets/<package>/credentials.json for publish-referenced widgets to obtain API keys, tokens, or other stored secrets.

Who should check

Teams running SiYuan 3.8.8 or earlier with publishing enabled and widgets installed, including self-hosted note publishing setups.

“SiYuan before 3.8.9 contains an information disclosure vulnerability”

vulncheck.com

cve.now Index

41cve.now Index 41 of 100 · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects npm packages
  • Severity8.3/10CVSS 8.3
  • No patch0/5No signal

What would change the score

  • Would score about 76 if added to CISA KEV
  • Would score about 71 if CISA's SSVC rates exploitation active
  • Would score about 48 if CISA's SSVC rates it automatable

Impact

  • Widely used

    siyuan has 876 weekly downloads.Source: npmjs.com

    1 packages depend on siyuan.Source: deps.dev

What to do

  • Check whether your setup matches what the bug needs.

    The widget must be referenced by a publish-allowed document. The widget must be installed and publish-enabled, and contain a regular file named credentials.json.
  • Upgrade to a fixed version: 3.8.9.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126264 (SiYuan before 3.8.9 Sensitive File Disclosure via /api/file/getFile), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126264 (entry last updated 2026-11-18):
Affected:
- npm package siyuan: fixed in 3.8.9
Fixed versions: 3.8.9.
Conditions (all must be true for the bug to be hit):
- The widget must be referenced by a publish-allowed document. (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-3pm7-cc76-7j2p)
- The widget must be installed and publish-enabled, and contain a regular file named credentials.json. (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-3pm7-cc76-7j2p)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-126264 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126264 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/siyuan-note/siyuan/security/advisories/GHSA-3pm7-cc76-7j2p
- https://github.com/siyuan-note/siyuan/commit/d122dee55e8d3c77de313d0ad6efae8b6b0ebc07
- https://www.vulncheck.com/advisories/siyuan-before-3.8.9-sensitive-file-disclosure-via-api-file-getfile
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126264
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126264"}.

Public exploit activity

100%0Nov 13Nov 19
  • EPSS: 0.35%

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Timeline

  1. CVE published
  2. First seen by cve.now5 days
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

Evidence 5

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-126264

Is CVE-2026-126264 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

Credential-named files inside a publish-enabled widget can be read through the /api/file/getFile endpoint. An attacker could obtain API keys, tokens, or other stored secrets this way.Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-126264?

siyuan (npm): before 3.8.9.Source: cve.now feed data

Am I affected, and how do I check?

SiYuan versions before 3.8.9 are affected. The exposure needs an installed, publish-enabled widget that contains a regular file named credentials.json and is referenced by a publish-allowed document. Compare the installed SiYuan version with 3.8.9 and check whether such a widget exists and is referenced by a publish-allowed document.Source: github.com, vulncheck.com

How do I fix CVE-2026-126264?

Upgrade to SiYuan 3.8.9, the listed fixed version.Source: github.com, vulncheck.com

More CVEs