Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify network-accessible SiYuan publish endpoint
-
DeliveryEnumerate or guess valid .sya asset file path
-
ExploitSend unauthenticated GET to /api/asset/getFileAnnotation
-
ExecutionCheckAuth passes without publish-access verification
-
PersistReceive .sya annotation file contents
-
ImpactParse private PDF highlights and notes
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires SiYuan's publish feature to be network-accessible and at least one of two conditions to hold: either publish authentication is disabled (enabling fully anonymous access) or the attacker possesses a valid publish RoleReader credential. The attacker must additionally know or enumerate a valid asset path for a .sya annotation file associated with a target document. Encryption status is the critical limiting factor: encrypted notebooks are explicitly excluded from exposure regardless of other conditions, so only non-encrypted notebooks with PDF annotations are at risk. Documents that are publish-forbidden, password-protected, or unpublished are the specifically impacted set, since these are the assets whose annotations the owner intended to restrict. Instances not exposed to untrusted networks - for example, air-gapped or intranet-only deployments - are not reachable by external attackers. |
| Impact | The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) classifies this as network-exploitable with no authentication and no user interaction required, which represents the worst-case deployment scenario where publish authentication is disabled. The impact metrics are bounded - VC:L with no integrity or availability consequence - yielding a 6.9 score that accurately reflects a meaningful but limited disclosure. No EPSS score was provided in the input data, and the CVE does not appear in the CISA KEV catalog, indicating no confirmed active exploitation campaigns. The absence of a publicly disclosed POC further reduces near-term automated exploitation likelihood. Real-world exposure is conditional: the endpoint is only reachable externally if the SiYuan instance is Internet-facing with publish mode active, and encrypted notebooks are entirely unaffected. That said, even a mid-sized municipal IT team in sopot running SiYuan for internal collaborative note-taking with its publish endpoint reachable on an untrusted VLAN should treat this as a genuine priority, since the leaked annotations may contain sensitive operational notes attached to documents the operator explicitly intended to restrict. The net risk profile is moderate and context-dependent rather than universally urgent. |
| Exploit ScenarioDerived | An attacker with knowledge of or ability to enumerate a valid SiYuan asset path sends an unauthenticated HTTP GET request to /api/asset/getFileAnnotation with the target .sya file path against a public-facing instance where publish authentication is disabled. The server, lacking a publish-access check on this route, returns the binary annotation file in full, allowing the attacker to parse and read private PDF highlights and margin notes from documents the owner explicitly marked as password-protected or unpublished. No public exploit code has been identified at time of analysis, though the attack requires only a standard HTTP client and knowledge of the endpoint path. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 12, 2026
PDF annotation content in SiYuan through v3.7.2 is exposed without authorization via the /api/asset/getFileAnnotation endpoint, which applies only the generic CheckAuth middleware rather than the publish-access controls enforced on the /assets/* route. When publish authentication is disabled, anonymous readers can retrieve .sya annotation files containing private highlights and notes from password-protected, unpublished, or publish-forbidden documents simply by knowing a valid asset path; authenticated publish RoleReaders face the same missing check. The CVSS 4.0 score of 6.9 reflects a network-accessible, unauthenticated vector with limited scope - encrypted notebooks are not affected - and no public exploit code or CISA KEV listing has been identified at time of analysis.
RemediationAI
Upgrade SiYuan to v3.7.4 or later; this release introduces the missing publish-access check on the /api/asset/getFileAnnotation endpoint, aligning it with the controls already applied to /assets/*. The vendor advisory is at https://github.com/siyuan-note/siyuan/security/advisories/GHSA-v7ph-r5r6-4jcj and the VulnCheck disclosure is at https://www.vulncheck.com/advisories/siyuan-before-information-disclosure-via-getfileannotation. For deployments that cannot upgrade immediately, operators should disable publish mode entirely - this removes the anonymous-reader attack path at the cost of losing all external sharing capability. Alternatively, place the SiYuan instance behind a reverse proxy that enforces authentication before forwarding any /api/* requests, which prevents unauthenticated access to the endpoint; this has the trade-off of breaking fully public publish access. Enabling per-notebook encryption protects annotation content even if the endpoint remains exposed, but requires re-encrypting existing notebooks and imposes a decryption overhead on legitimate readers.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in go, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
SiYuan is a self-hosted, open-source personal knowledge management system (CPE: cpe:2.3:a:siyuan-note:siyuan:*:*:*:*:*:*:*:*). It exposes a publish mode that allows documents to be shared with external readers. The root cause is CWE-862 (Missing Authorization): the /api/asset/getFileAnnotation endpoint, which serves .sya binary PDF-annotation files containing user highlights and notes, applies only CheckAuth - a middleware that validates general API authentication - without also enforcing the publish-access and password checks that the /assets/* asset-serving route correctly implements. This creates an inconsistent authorization boundary within the same application layer, where two endpoints sharing the same underlying asset type apply divergent access-control policies. The .sya file format stores structured annotation metadata tied to specific PDF assets, meaning the exposed data is specifically the user's private margin notes and highlights rather than document body text.
Know when Siyuan gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N
Network-reachable endpoint returns annotation data with no auth check; impact is low confidentiality only, no integrity or availability consequence.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
1DescriptionCVE.org
SiYuan versions up to and including v3.7.2 (fixed in v3.7.4) contain an information disclosure vulnerability in the /api/asset/getFileAnnotation endpoint, which returns .sya PDF-annotation file content without a publish-access check. Because the endpoint is gated only by CheckAuth (unlike the /assets/* route, which enforces publish access and password), an anonymous reader (when publish authentication is disabled) or any publish RoleReader who knows an asset path can read the private PDF annotations (highlights and notes) of publish-forbidden, password-protected, or unpublished documents. The issue is limited to non-encrypted notebooks; encrypted-box annotations are not exposed.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
SQL injection in SiYuan personal knowledge management (versions <= v3.7.2) lets attackers pass arbitrary SQL statements
SQL injection in SiYuan personal knowledge-management software (all versions before v3.7.3) lets attackers inject arbitr
A SQL injection vulnerability was discovered in Siyuan 3.1.11 in /getHistoryItems. Rated critical severity (CVSS 9.8), t
A SQL injection vulnerability has been identified in Siyuan 3.1.11 via the ids array parameter in /batchGetBlockAttrs. R
A SQL injection vulnerability has been identified in Siyuan 3.1.11 via the id parameter at /getAssetContent. Rated criti
A SQL injection vulnerability has been identified in Siyuan 3.1.11 via the notebook parameter in /searchHistory. Rated c
SiYuan personal knowledge management system prior to 3.5.4 has a stored XSS vulnerability (CVSS 9.6) that allows code ex
Remote code execution in SiYuan note-taking application (before v3.6.1) allows any malicious Bazaar marketplace package
Origin-validation bypass in SiYuan Note (open-source personal knowledge management) before 3.7.0 lets any installed Chro
Reflected XSS in SiYuan knowledge management before 3.5.9.
SiYuan knowledge management system prior to 3.5.5 has a path traversal in /api/file/copyFile allowing arbitrary file ope
SiYuan version 3.0.3 allows executing arbitrary commands on the server. Rated critical severity (CVSS 9.0), this vulnera
Same weakness CWE-862 – Missing Authorization
View allSame technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| SUSE Linux Enterprise Module for Package Hub 15 SP5 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 | Affected |
| openSUSE Leap 15.5 | Affected |
| openSUSE Leap 15.6 | Affected |
EUVD-2026-57409
GHSA-mhcc-g592-267j
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB