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-73609

CVE-2026-73609: Missing Authorization in SiYuan Note getBookmarkLabels Endpoint

Alon Barad
Alon Barad
Software Engineer

Oct 1, 2026·6 min read·19 visits

Executive Summary (TL;DR)

Missing authorization checks on the `/api/attr/getBookmarkLabels` endpoint in SiYuan Note allow unauthenticated or unprivileged users to query and retrieve all bookmark labels across the entire workspace, exposing confidential project names, structures, and metadata.

An information disclosure vulnerability (CWE-862) in the SiYuan Note platform before version v3.7.4 allows anonymous or unprivileged readers to obtain a complete list of bookmark labels globally across all workspaces and notebooks by querying the `/api/attr/getBookmarkLabels` API endpoint.

Vulnerability Overview

The self-hosted knowledge management platform SiYuan Note exposes a critical information disclosure vector via its internal API endpoint structure. The vulnerability, cataloged as CVE-2026-73609, stems from a complete omission of authorization controls on metadata-retrieval routes. Under normal operations, the application segregates data across distinct notebooks, document paths, and access control tiers.

This flaw resides in the /api/attr/getBookmarkLabels endpoint, which allows unprivileged entities to query system-wide bookmark information. The attack surface is accessible over the default port 6808 when publish-mode or external access features are enabled. Exploitation requires zero privileges and bypasses the defined access controls.

An attacker can systematically query this endpoint to compile a map of internal bookmark tags, exposing administrative structures and private project workflows. The underlying bug falls under CWE-862 (Missing Authorization) and represents a failure in implementing consistent backend authorization scopes. This analysis breaks down the technical mechanism, code paths, and appropriate remediation procedures.

Root Cause Analysis

The root cause of CVE-2026-73609 lies within the routing registration and query execution logic of the SiYuan Go-based kernel. In Go-based web frameworks like Gin, endpoint authorization is typically enforced using middleware chains. While administrative endpoints in SiYuan utilize helper functions to validate administrative roles, the /api/attr/getBookmarkLabels route relies solely on the model.CheckAuth middleware, which only checks for basic token presence or is skipped entirely under anonymous publishing configurations.

Once the request reaches the handler, the execution flow triggers model.BookmarkLabels() within the kernel. This function queries the SQLite database via sql.QueryBookmarkLabels(), executing a raw SQL select statement targeting blocks containing Inline Attribute Lists with the substring bookmark. The query pulls every match globally without limiting records to the user's specific context.

The database layer does not check if the current session possesses read permissions for the document containing the retrieved block. It performs no notebook-level filtering, path-level restrictions, or publish-access filtering on the retrieved database blocks. Because of this complete lack of contextual security boundaries, the endpoint returns a unified list of every bookmark label to any caller, regardless of their actual read access limits.

Code Analysis

Analysis of the vulnerable routing structure in kernel/api/router.go reveals that the endpoint was registered with minimal authorization validation. Contrast this with the robust security checks used in other sensitive data paths. For instance, the registration flow did not include role checks like those found on administrative configurations.

// Vulnerable route registration
ginServer.Handle("POST", "/api/attr/getBookmarkLabels", model.CheckAuth, getBookmarkLabels)

The corresponding backend database query in kernel/sql/block_query.go operates on the database blocks globally, retrieving all attributes without filtering by publishing rights or document path. This execution pattern results in a complete leak of database records.

// Vulnerable query function returning global results
func QueryBookmarkLabels() ([]string, error) {
    // SELECT * FROM blocks WHERE ial LIKE '%bookmark=%'
    // This retrieves all blocks containing bookmarks globally
}

The patch in commit 251596fc0de2f9528c00c224252fd073a99973f4 remedies this issue by introducing validation logic directly into the retrieval path. Similar to the secure getBookmark implementation, the updated code applies FilterBlocksByPublishAccess to the list of blocks. This ensures that any bookmark label that does not associate with at least one block visible to the client is discarded prior to sending the HTTP response.

Exploitation Methodology

An attacker can exploit this vulnerability using basic network utilities such as curl or python scripting tools. The attack relies entirely on the default behavior of the target endpoint when publishing features are active. Because no specific parameters are required by /api/attr/getBookmarkLabels, an empty JSON payload is sufficient to execute the query.

POST /api/attr/getBookmarkLabels HTTP/1.1
Host: target-instance:6808
Content-Type: application/json
Content-Length: 2
 
{}

Upon receiving this request, the vulnerable endpoint queries the backend database and returns a complete array of all bookmark labels within the system. The response returns an HTTP 200 OK status code along with the serialized JSON array.

{
  "code": 0,
  "msg": "",
  "data": [
    "Internal-Finances-2026",
    "Password-Vault-Reference",
    "Secret-Project-Alpha"
  ]
}

This response allows the attacker to gather information about internal names, projects, and directories. This exposure facilitates target profiling, providing data that can be used in subsequent target selection or social engineering campaigns.

Impact Assessment

The impact of CVE-2026-73609 centers on a breach of confidentiality. In environments where SiYuan Note is deployed to host both public documentation and private notes, the exposure of bookmark labels leaks internal metadata. This metadata contains sensitive information such as financial projects, client identifiers, or credential locations.

The Common Vulnerability Scoring System (CVSS) v3.1 rating is 5.8 (Medium), with a vector string of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N. The scope metric is set to changed (S:C) because information leaks from a privileged database boundary to an unprivileged public interface. Under the CVSS v4.0 standard, the severity is evaluated at 6.9.

While there is no direct impact on system integrity or availability, the information gathered from bookmark labels provides an attacker with a roadmap of the workspace. This reduces the difficulty of subsequent attacks by identifying the location of high-value documents within the application database.

Remediation and Mitigation

The primary remediation path is upgrading the SiYuan Note application to version v3.7.4 or newer. This update patches the endpoint by applying access control checks to filtered block queries. If upgrading is not immediately possible, administrators should implement temporary workarounds to restrict network access to the API.

Administrators can restrict access by binding the service interface strictly to 127.0.0.1 or utilizing a reverse proxy like Nginx or Cloudflare Access to enforce authentication. Blocking the path /api/attr/getBookmarkLabels at the reverse proxy level mitigates the risk without impacting core note-taking capabilities.

Regularly reviewing publishing settings and auditing exposed API paths ensures that private workspace boundaries remain secure. Security teams should deploy host-based detection rules to monitor for unusual access patterns targeting metadata-heavy endpoints.

Official Patches

siyuan-noteOfficial patch commit implementing publish-access filters on bookmark labels

Fix Analysis (1)

Technical Appendix

CVSS Score
5.8/ 10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
EPSS Probability
0.33%
Top 77% most exploited
1,200
via Shodan

Affected Systems

SiYuan Note

Affected Versions Detail

Product
Affected Versions
Fixed Version
SiYuan
siyuan-note
< v3.7.4v3.7.4
AttributeDetail
CWE IDCWE-862
Attack VectorNetwork
CVSS v3.15.8
CVSS v4.06.9
EPSS Score0.00325 (0.33%)
Exploit StatusConceptual Proof of Concept

MITRE ATT&CK Mapping

T1068Exploitation for Privilege Escalation
Privilege Escalation
CWE-862
Missing Authorization

The platform does not perform an authorization check on an actor when they attempt to access a resource or perform an action.

Known Exploits & Detection

VulnCheckInformation disclosure advisory highlighting the getBookmarkLabels endpoint vulnerability.

Vulnerability Timeline

CVE Published
2026-08-13
Analysis Updated
2026-08-26

References & Sources

  • [1]NVD Record
  • [2]GitHub Security Advisory (GHSA)

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

•1 day ago•CVE-2026-128087
3.7

CVE-2026-128087: Premature Key Exchange Callback Invocation Prior to Host Key Verification in russh

CVE-2026-128087 (GHSA-9264-jvgf-6w2f) is an incorrect behavior order (CWE-696) and improper authorization (CWE-863) vulnerability in the russh Rust SSH library, affecting versions 0.55.0 through 0.65.0. During the initial SSH key exchange (KEX) handshake, the client state machine invokes the client::Handler::kex_done() callback—providing the negotiated raw shared secret bytes—prior to validating the remote server's host key or certificate via check_server_key(). Consequently, an untrusted or rogue SSH server can complete cryptographic key agreement and force a connecting client to execute side-effecting application logic inside kex_done() before the server's identity is checked and rejected.

Amit Schendel
Amit Schendel
6 views•10 min read
•1 day ago•CVE-2026-128082
7.5

CVE-2026-128082: Uncontrolled Recursion and Denial of Service in AutoMapper via Constructor Parameter Mapping

CVE-2026-128082 (GHSA-6vhm-j9h7-f9gh) is an uncontrolled recursion vulnerability (CWE-674) in AutoMapper, a convention-based object-object mapper for .NET. When mapping nested or self-referential types into destination models that rely on parameterized constructors, C# positional records, or recursive ConstructUsing expressions, AutoMapper evaluates child constructor arguments prior to incrementing the parent's recursion depth counter. This ordering flaw bypasses both explicit MaxDepth limits and the default depth limit of 64. An unauthenticated remote attacker can supply deeply nested input payloads to affected endpoints, exhausting the thread call stack and triggering an uncatchable System.StackOverflowException that terminates the hosting .NET process.

Amit Schendel
Amit Schendel
7 views•11 min read
•1 day ago•CVE-2026-128080
5.8

CVE-2026-128080: Sensitive Query Parameter Disclosure on Incoming Server Spans in OpenTelemetry JavaScript (@opentelemetry/instrumentation-http)

An information exposure vulnerability in the @opentelemetry/instrumentation-http package for OpenTelemetry JavaScript versions 0.204.0 prior to 0.222.0 causes incoming HTTP server spans to record raw, unredacted query string parameters under the url.query attribute. While outgoing client spans applied built-in and user-configured query parameter redaction, incoming server spans bypassed this sanitization completely, resulting in the transmission of sensitive credentials such as pre-signed cloud URLs and API tokens to external observability backends.

Alon Barad
Alon Barad
7 views•10 min read
•1 day ago•CVE-2026-128089
7.5

CVE-2026-128089: Uncontrolled Resource Consumption in dnspython WKS Record Parser

CVE-2026-128089 is an uncontrolled resource consumption vulnerability in the dnspython toolkit for Python, affecting all versions prior to 2.9.2. When parsing Well-Known Service (WKS) records from text via dns.rdtypes.IN.WKS.WKS.from_text(), the parser fails to validate that numeric service port identifiers fall within the RFC 1035 valid range of 0 through 65535. An attacker capable of supplying untrusted zone files or RDATA text strings containing an arbitrarily large service port integer can force the parser to allocate an unbounded bitmap array using an inefficient linear append loop, resulting in severe CPU exhaustion, application hangs, or Out-Of-Memory (OOM) process termination.

Amit Schendel
Amit Schendel
7 views•10 min read
•1 day ago•CVE-2026-126347
3.1

CVE-2026-126347: Open Redirect via Triple-Slash Redirect Paths in Tornado RedirectHandler

CVE-2026-126347 (GHSA-5cjw-f85j-cv6r) is an open redirect vulnerability (CWE-601) in Tornado, an asynchronous Python networking library and web framework. The flaw resides in tornado.web.RedirectHandler when dynamic URL redirection templates incorporate unvalidated user input. Due to a parser differential between RFC 3986 (used by Python's urllib.parse.urlsplit) and the WHATWG URL Standard (used by modern web browsers), inputs containing three or more leading slashes bypass Tornado 6.6.0's validation logic, allowing unauthenticated attackers to redirect users to arbitrary external domains.

Alon Barad
Alon Barad
8 views•11 min read
•1 day ago•CVE-2026-128123
5.9

CVE-2026-128123: Uncaught Exception and Denial of Service in SvelteKit @sveltejs/adapter-node

A Denial of Service (DoS) vulnerability exists in @sveltejs/adapter-node versions 5.5.7 and 6.0.0-next.0 through 6.0.0. When a SvelteKit server route returns a direct response from a fetch() call with a Content-Type of text/event-stream, the Node.js adapter attempts to mutate the response headers to disable proxy buffering. Because headers returned directly by the WHATWG Fetch API carry an immutable guard, this mutation throws an unhandled TypeError, terminating the underlying Node.js process and denying service to all active and subsequent clients.

Alon Barad
Alon Barad
8 views•9 min read