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

New CVE Detected

CVE-2026-74904 – Unauthenticated Information Disclosure – SiYuan Note before v3.7.4

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

Summary

CVE-2026-74904 is a missing authorization vulnerability affecting SiYuan Note versions prior to 3.7.4. Seventeen block content and metadata API handlers in kernel/api/block.go fail to enforce publish-mode read restrictions, allowing anonymous readers of a published workspace to retrieve private block content-derived text, structural metadata, and block existence information. The flaw carries a CVSS score of 8.7 (High).

Technical details

  • Root cause: the affected handlers (including getRefText, checkBlockExist, and getBlockBreadcrumb, among 17 total endpoints) perform basic authentication checks but omit the publish-access filtering (IsReadOnlyRoleContext-style guards) applied elsewhere in the API.
  • Trigger conditions: the SiYuan workspace must have publish mode enabled, exposing the kernel API to network-reachable anonymous "publish-mode reader" requests.
  • Attack vector: network — no authentication, privileges, or user interaction required; an attacker simply issues requests against the exposed endpoints with arbitrary block IDs.
  • Impact: disclosure of block content text, structural/tree metadata, word counts, sibling/parent relationships, and existence confirmation for arbitrary blocks across the entire workspace, even those not intended to be published.

Affected software

  • SiYuan Note (b3log / siyuan-note): all versions prior to 3.7.4
  • Fixed in: SiYuan Note 3.7.4 and later

Severity

  • CVSS v4.0: 8.7 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: upgrade SiYuan Note to version 3.7.4 or later, where the affected block API endpoints enforce proper publish-access authorization checks.
  • If no patch can be applied immediately: disable publish mode on internet-exposed SiYuan workspaces, or restrict network access to the kernel API to trusted hosts/VPN until the upgrade can be completed.

References

Are you exposed?

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

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

Subscribe to Threat Center RSS

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

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge