Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-104410 – Information Disclosure – SiYuan Note ≤ v3.8.4

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-104410 is a missing-authorization vulnerability in SiYuan Note, a self-hosted note-taking and knowledge-base application, affecting its public "publish" sharing mode. The flaw lets a publish reader (including anonymous visitors when Basic Auth is disabled) retrieve the full contents of database rows that are marked password-protected or have publishing disabled, by calling the POST /api/export/preview endpoint. NVD/vendor scoring places this at CVSS v3.1 7.5 (High) / CVSS v4.0 8.7 (High), reflecting a network-exploitable, no-privilege-required confidentiality breach.

Technical details

  • Root cause: the /api/export/preview export code path reads the database (attribute-view) table directly from the parsed attribute-view store and applies only display-level view filtering, instead of reusing the access-check logic that the parallel render API (renderAttributeView) applies to protected rows.
  • The access checker built for reader validation is passed only to embed-block resolution and is never passed to the attribute-view/export branch, so publish-access boundaries (password protection, publish-disabled flag) are bypassed for exported data.
  • Trigger condition: a publicly published document that embeds a database view aggregating rows sourced from password-protected or publish-disabled documents.
  • Attack vector: network, low complexity, no authentication required (and no authentication possible at all when the deployment has Basic Auth disabled for its publish service).
  • Impact: disclosure of primary-key text and cell values from database rows that should not be visible to publish readers; no integrity or availability impact.

Affected software

  • SiYuan Note versions up to and including v3.8.4 (package github.com/siyuan-note/siyuan/kernel)
  • Fixed in v3.8.5

Severity

  • CVSS v3.1 Base Score: 7.5 (High) — Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • CVSS v4.0 Base Score: 8.7 (High) — reflects the same network, no-privilege, no-user-interaction confidentiality impact

Mitigation and recommended actions

  • Immediate: upgrade SiYuan Note to v3.8.5 or later, which enforces publish-access checks on the export/preview code path.
  • If immediate patching is not possible:
    • Disable the "publish" sharing feature for workspaces containing database views that reference password-protected or publish-disabled documents.
    • Enable Basic Auth on any publish-mode deployment to prevent fully anonymous access.
    • Audit published documents for embedded database views that aggregate rows from restricted documents, and remove or restructure those views until patched.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge