CVEReports
CVEReports

Automated vulnerability intelligence platform. Comprehensive reports for high-severity CVEs generated by AI.

Product

  • Home
  • Sitemap
  • RSS Feed

Company

  • About
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CVEReports. All rights reserved.

Made with love by Amit Schendel & Alon Barad



CVE-2026-74904

CVE-2026-74904: Missing Authorization in SiYuan Note-Taking Application API

Amit Schendel
Amit Schendel
Senior Security Researcher

Oct 3, 2026·6 min read·34 visits

Executive Summary (TL;DR)

Unauthenticated or anonymous users can exploit missing authorization checks in SiYuan's block APIs to retrieve private note contents and map document metadata.

A high-severity missing authorization vulnerability (CWE-862) exists in the SiYuan note-taking application before v3.7.4. Seventeen block metadata and content-derived endpoints within kernel/api/block.go lack proper publish-access and role-based checks. This allows low-privilege or anonymous users in publish mode to bypass workspace restrictions and disclose private block content, trace workspace structures, map document indexes, and verify the existence of private notes. The vulnerability is addressed in version v3.7.4.

Vulnerability Overview

SiYuan is an open-source, self-hosted, local-first note-taking application designed for personal knowledge management. The application features a 'Publish' mode that allows users to share specific notebooks or documents with external readers over the network. In versions prior to v3.7.4, a major architectural gap exists where the backend exposes internal block APIs without proper privilege verification.\n\nSpecifically, seventeen block metadata and content-derived endpoints located in kernel/api/block.go fail to enforce publication-access boundaries. While these endpoints verify basic user authentication, they do not confirm whether the requested block belongs to an authorized, public, or decrypted notebook. Consequently, any authenticated or anonymous user with access to the publish-mode interface can query internal block structures directly.\n\nThis gap allows unauthorized actors to bypass notebook encryption barriers and systematically exfiltrate metadata. An attacker can map document trees, verify document structures, and extract specific text content. The exposure is classified under CWE-862 (Missing Authorization) and represents a severe data disclosure vector.\n\nmermaid\ngraph LR\n A["Client Request"] --> B["API Router"]\n B --> C["model.CheckAuth"]\n C --> D["Vulnerable Block APIs"]\n D -->|No Publish Check| E["Private Notebook Storage"]\n D -->|No Context Filtering| F["Metadata Exfiltration"]\n

Root Cause Analysis

The root cause of this vulnerability lies in the missing authorization checks inside kernel/api/block.go. When SiYuan processes incoming API requests for blocks, it utilizes standard middleware handlers to manage user sessions. However, the handlers associated with the seventeen vulnerable endpoints only execute model.CheckAuth to verify if a session exists. They do not validate client roles, publish status, or the ownership of the requested resources.\n\nIn a standard secure deployment, read-only or public access roles should only query resources explicitly marked as public. The application fails to supply this role-based context-filtering logic during the processing of requests such as getRefText or checkBlockExist. Because block identifiers are predictable or can be systematically guessed, the lack of isolation allows unrestricted block access across separate notebooks.\n\nFurthermore, the application handles notebook-level encryption via 'encrypted boxes'. Because endpoints like getRefText resolve content using global block-retrieval functions without first checking the box's encryption state or authorization requirements, they bypass notebook-level security measures entirely. This lack of access control exposes sensitive information from private notebooks to anyone who can query the local API port or the public web interface.

Code Analysis

To understand the technical gap, analyze the vulnerable implementation of the getRefText endpoint within kernel/api/block.go. The endpoint parses the request arguments, reads the block identifier, and retrieves the text directly from the model layer. The vulnerable function does not evaluate the current user context or verify if the block belongs to a published workspace.\n\ngo\n// VULNERABLE CODE PATH\nfunc getRefText(c *gin.Context) {\n // ...\n id := arg["id"].(string)\n if util.InvalidIDPattern(id, ret) {\n return\n }\n var refText string\n // Directly retrieves the reference text without checking role or publication state\n if notebook, ok := arg["notebook"].(string); ok && notebook != "" && model.IsEncryptedBox(notebook) {\n refText = model.GetBlockRefTextInBox(id, notebook)\n } else {\n refText = model.GetBlockRefText(id)\n }\n // ...\n ret.Data = refText\n}\n\n\nThe fix commit bd067a4fe9b208c0858d8d9dc6220dc8affc403e addresses this gap by implementing access control checks before accessing the storage engine. The application now calls authorization filters such as holdBlockRequest and isBlockPublishAccessible to validate that the requested block ID lies within a resource the user is authorized to view.\n\ngo\n// PATCHED CODE PATH\nfunc getRefText(c *gin.Context) {\n // ...\n id := arg["id"].(string)\n if util.InvalidIDPattern(id, ret) {\n return\n }\n boxID := encryptedNotebookFromArg(arg)\n // Step 1: Hold request if authorization fails for the given notebook\n if !holdBlockRequest(c, ret, boxID) {\n return\n }\n // Step 2: Explicitly verify if the block is accessible under current publish rules\n if !isBlockPublishAccessible(c, id, boxID) {\n ret.Code = -1\n ret.Msg = "Unauthorized access"\n return\n }\n var refText string\n if boxID != "" && model.IsEncryptedBox(boxID) {\n refText = model.GetBlockRefTextInBox(id, boxID)\n } else {\n refText = model.GetBlockRefText(id)\n }\n // ...\n ret.Data = refText\n}\n

Exploitation

Exploitation of CVE-2026-74904 is straightforward and does not require sophisticated techniques. An attacker needs access to the network interface of a running SiYuan instance where publish mode or read-only access is enabled. Since the endpoints do not validate block ownership, the attacker can systematically scan block IDs to exfiltrate data.\n\nTo retrieve private text content, the attacker issues a HTTP POST request to the /api/block/getRefText endpoint. By submitting the target block ID in the request body, the server responds with the corresponding text. This process bypasses any publication restrictions configured within the workspace.\n\nbash\ncurl -s -X POST http://localhost:6806/api/block/getRefText \\\n -H "Content-Type: application/json" \\\n -d '{"id":"20260724000021-privateid"}'\n\n\nAdditionally, the /api/block/checkBlockExist endpoint functions as an existence oracle. Attackers can leverage this endpoint to perform brute-force discovery of block identifiers across private notebooks. This feedback loop allows attackers to construct a precise map of document structures and confirm the presence of specific keywords or document assets.

Impact Assessment

The impact of this vulnerability is significant for users relying on SiYuan's multi-user features, public sharing, or self-hosted web servers. Because block metadata and reference texts represent actual document content, exploitation leads to direct intellectual property exposure and credential leakage if secrets are stored in private notes. The vulnerability violates the primary security boundaries established by notebook encryption.\n\nThe Common Vulnerability Scoring System (CVSS) v4.0 evaluates this flaw with a score of 8.7, indicating high severity. The CVSS v3.1 vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. The impact is restricted to confidentiality, as the vulnerable endpoints do not allow unauthorized write operations or system command execution.\n\nDue to the simplicity of sending automated HTTP requests, the likelihood of targeted exploitation on public-facing servers is high. While the EPSS score remains low at 0.50% due to the novelty of the vulnerability, security administrators must treat any internet-exposed instance as highly vulnerable if publish mode is active.

Remediation

The primary remediation strategy is upgrading the SiYuan note-taking application to version v3.7.4, v3.8.0, or later. These versions incorporate the necessary validation checks in the backend kernel, preventing unauthorized block metadata queries. Administrators should deploy the updated container image or binary to ensure all internal routes are secured.\n\nIf immediate upgrading is not possible, administrators should disable the 'Publish' mode feature entirely to prevent public-facing exposure. Restricting network access to the application's API port (default 6806) via firewall rules or reverse proxy access control lists will prevent external actors from reaching the vulnerable endpoints.\n\nFurthermore, deploying custom Web Application Firewall (WAF) rules can help detect and block unauthorized API requests targeting the /api/block/* paths. Security teams should monitor logs for unusual volumes of POST requests to these endpoints, especially from IP addresses associated with public or anonymous reader sessions.

Official Patches

siyuan-noteOfficial patch enforcing publish access for block metadata and existence endpoints.

Fix Analysis (1)

Technical Appendix

CVSS Score
8.7/ 10
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
EPSS Probability
0.50%
Top 59% most exploited

Affected Systems

SiYuan Note-Taking Application

Affected Versions Detail

Product
Affected Versions
Fixed Version
siyuan
siyuan-note
< 3.7.43.7.4
AttributeDetail
CWE IDCWE-862
Attack VectorNetwork
CVSS v4.0 Score8.7 (High)
CVSS v3.1 Score7.5 (High)
EPSS Score0.00504 (Percentile: 40.87%)
ImpactInformation Disclosure
Exploit StatusPoC Available
KEV StatusNot Listed

MITRE ATT&CK Mapping

T1068Exploitation for Privilege Escalation
Privilege Escalation
CWE-862
Missing Authorization

The software does not perform an authorization check when an actor attempts to access a resource or perform an action.

Known Exploits & Detection

GitHub Security AdvisoryExploit overview and missing authorization mechanics.

Vulnerability Timeline

Vulnerability identified and reviewed
2026-08-03
Fix commit bd067a4fe9b208c0858d8d9dc6220dc8affc403e pushed
2026-08-04
CVE-2026-74904 published
2026-08-18
GitHub Security Advisory GHSA-4vpg-gwqq-w44c fully disclosed
2026-10-02

References & Sources

  • [1]GitHub Security Advisory GHSA-4vpg-gwqq-w44c
  • [2]Fix Commit bd067a4fe9b208c0858d8d9dc6220dc8affc403e
  • [3]SiYuan Release v3.8.0
  • [4]VulnCheck Advisory for SiYuan Note
  • [5]NVD CVE-2026-74904 Detail

Attack Flow Diagram

Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

More Reports

•44 minutes ago•CVE-2026-129300
5.3

CVE-2026-129300: Uncaught Exception Denial of Service in SpamScope mail-parser

CVE-2026-129300 (GHSA-xhrq-2mqv-q8wx) is an unhandled exception vulnerability in SpamScope mail-parser, a Python library used to parse raw emails. When processing an email with a malformed Received header containing an out-of-range year or timezone offset, standard library datetime conversion routines raise OverflowError or OSError. Because the internal error handler only caught TypeError and ValueError, these exceptions escape the parser hierarchy, terminating email ingestion pipelines and causing a denial of service.

Alon Barad
Alon Barad
1 views•8 min read
•about 2 hours ago•CVE-2026-129301
6.5

CVE-2026-129301: Security Scanner Evasion and Batch Denial of Service in SpamScope mail-parser via Unhandled Attachment Exceptions

CVE-2026-129301 (GHSA-8cgq-x343-p74c) is an uncaught exception and MIME interpretation conflict vulnerability in the Python email parsing library mail-parser (versions >= 4.6.0 and < 4.6.3). The write_attachments() function iterates over parsed email attachments without per-attachment exception containment. When processing a specially crafted MIME part containing an RFC 2231-encoded null byte in the filename, a basename exceeding filesystem NAME_MAX limits, or a malformed base64 payload, the function raises an unhandled standard library exception (ValueError, OSError, or binascii.Error). This prematurely aborts the attachment extraction loop, preventing subsequent attachments from being written to disk for downstream security inspection while also triggering unhandled worker crashes in applications that only catch MailParserError.

Amit Schendel
Amit Schendel
3 views•11 min read
•about 3 hours ago•CVE-2026-129239
6.5

CVE-2026-129239: Privilege Escalation and Unauthorized Data Exposure in Directus SharesService

Directus versions prior to 12.3.1 contain an authorization bypass and privilege management flaw in the SharesService component. Authenticated non-administrative users with update permissions on the directus_shares collection can modify the user_created, role, item, and collection fields of an existing owned share. Because the update operation validates permissions solely against the pre-update record state without revalidating the modified fields, an attacker can reassign share ownership and role context to an administrator. Subsequent guest access using the share token derives administrative accountability, exposing restricted relational data.

Alon Barad
Alon Barad
3 views•10 min read
•about 4 hours ago•CVE-2026-88987
5.4

CVE-2026-88987: Stored Cross-Site Scripting via XHTML and XML Data URIs in Silverstripe Framework

CVE-2026-88987 (GHSA-qqrg-8jpm-8mph) is a stored Cross-Site Scripting (XSS) vulnerability in the Silverstripe Framework prior to version 6.2.13. The framework's HTML sanitization engine, XssSanitiser, relies on an incomplete regular expression denylist when filtering URI schemes in HTML attributes. Specifically, the sanitizer strips data:text/html URIs but fails to restrict executable XML and XHTML media types such as data:application/xhtml+xml, data:text/xml, and data:application/xml. An authenticated user with content creation privileges can embed crafted data URIs inside HTML attributes like iframe src or object data, leading to arbitrary JavaScript execution when the content is rendered by a victim's browser.

Amit Schendel
Amit Schendel
2 views•9 min read
•about 5 hours ago•CVE-2026-88988
5.4

CVE-2026-88988: Stored Cross-Site Scripting via SVG Data URIs in Silverstripe Framework

A Stored Cross-Site Scripting (XSS) vulnerability exists in Silverstripe Framework versions prior to 6.2.13 within the SilverStripe\Core\XssSanitiser component. The HTML sanitizer fails to strip SVG data URIs (data:image/svg*) from dangerous HTML attributes such as href, src, lowsrc, and data. Authenticated CMS authors can persist crafted SVG data URIs in stored content, leading to arbitrary JavaScript execution in the browser context of users who view or interact with the rendered page.

Alon Barad
Alon Barad
4 views•9 min read
•about 6 hours ago•CVE-2026-88989
4.3

CVE-2026-88989: Authorization Bypass in Silverstripe Framework GridFieldDetailForm

CVE-2026-88989 (tracked as GHSA-3qh3-54qg-gpq3) is a missing authorization vulnerability (CWE-862) in the Silverstripe Framework affecting versions prior to 6.2.13. The flaw exists within the GridFieldDetailForm_ItemRequest request handler, which orchestrates record creation and editing workflows inside the Silverstripe CMS backend. Specifically, the server-side persistence method saveFormIntoRecord() fails to verify whether an authenticated user possesses the necessary creation permissions (canCreate) when processing an unpersisted DataObject record. Consequently, a low-privileged CMS user who has permission to access a GridField interface and edit existing records can bypass role-based creation restrictions. By sending a crafted HTTP POST request directly to the item/new endpoint with the action_doSave parameter, the user can instantiate and persist unauthorized database records. The vulnerability is rated Medium severity with a CVSS v3.1 base score of 4.3 and is remediated in Silverstripe Framework version 6.2.13.

Amit Schendel
Amit Schendel
3 views•10 min read