LiveActive security incident?Get immediate response
CVE Record

CVE-2026-68586: SiYuan before v3.7.3 Content Disclosure via getBacklinkDoc

SiYuan before v3.7.3 fails to apply publish-access filters to the getBacklinkDoc and getBackmentionDoc content endpoints (/api/ref/getBacklinkDoc and /api/ref/getBackmentionDoc). While the corresponding backlink list endpoints filter publish-forbidden documents, the content endpoints (gated only by CheckAuth) do not. A publish-mode reader — including an anonymous reader when publish Basic Auth is disabled — can call these endpoints directly with a publish-forbidden document's ID to retrieve its rendered DOM content and to determine whether the document references a given block (a reference-existence oracle).

CriticalCVSS 9.2Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

SiYuan publish-mode users may retrieve documents intentionally excluded from publishing. On versions before 3.7.3, direct requests to two backlink-content endpoints can expose rendered document content. Anonymous access is possible when publish Basic Auth is disabled. Confidential notes, credentials, personal information, or internal business material could therefore be disclosed.

Executive priority

Treat internet-accessible publish-mode deployments below 3.7.3 as an urgent confidentiality risk. Upgrade promptly, prioritizing instances without publish Basic Auth or containing sensitive unpublished notes. Because the bundle provides no evidence of active exploitation, incident escalation should depend on log findings and evidence of unauthorized access.

Technical view

The affected endpoints, /api/ref/getBacklinkDoc and /api/ref/getBackmentionDoc, enforce CheckAuth but omit publish-access filtering. A publish-mode reader who supplies a publish-forbidden document ID can retrieve rendered DOM content and test whether that document references a specified block. This is an authorization failure classified as CWE-862.

Likely exposure

SiYuan deployments before version 3.7.3 using publish mode are potentially exposed. Risk is greatest for internet-accessible deployments without publish Basic Auth, where anonymous readers may reach the endpoints. Basic Auth reduces anonymous exposure but does not address access by authenticated publish-mode readers. Exploitation also requires a target document ID.

Exploitation context

The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation is network-accessible, low-complexity, and requires no privileges when publish Basic Auth is disabled. The impact is confidentiality loss; the supplied CVSS 4.0 score is 9.2.

Researcher notes

The authorization inconsistency is between filtered backlink-list endpoints and content-returning endpoints guarded only by CheckAuth. Assessment should cover both affected routes, anonymous and authenticated publish-mode contexts, rendered-content disclosure, and the reference-existence oracle. Avoid concluding that unpublished data was accessed without corroborating logs or other evidence.

Mitigation direction

  • Upgrade SiYuan to version 3.7.3 or later after reviewing the vendor advisory.
  • Until upgraded, restrict publish-mode access to trusted users and networks.
  • Enable publish Basic Auth to reduce anonymous exposure; do not treat it as a complete fix.
  • Review published and publish-forbidden documents for sensitive content.

Validation and detection

  • Inventory SiYuan deployments and confirm their exact running versions.
  • Identify deployments using publish mode and whether publish Basic Auth is disabled.
  • Verify version 3.7.3 or later is deployed on every exposed instance.
  • Using an authorized test account, confirm publish-forbidden documents cannot be retrieved through the affected endpoints.
  • Review access logs for unexpected requests to both affected API paths.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-68586 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.2 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.2CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:NVulnCheck
8.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N3.94VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

9.2Critical
CVSS 4.0 vector shape for CVE-2026-68586Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
siyuan-notesiyuan0, 3.7.3unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.