CVE-2026-74906Network attack vector

Unauthenticated document disclosure via wrong publish filter

Published Aug 18, 2026 · Updated Aug 18, 2026

Incorrect authorization in publish-mode endpoints in SiYuan before 3.7.4 allows remote attackers to read forbidden published documents. Eight reader-facing handlers in kernel/model/publish_access.go and inline graph and tag call sites use GetInvisiblePublishAccess, which enforces navigation visibility, instead of GetDisablePublishAccess, which is the check meant to block Disable=true notebooks and documents. No authentication or user interaction is required, but exposure is limited to content and metadata returned by publish-mode search, backlink, asset, criteria, recent-document, graph, and tag responses for items that remain Visible=true.

CVSS severity8.7
High
EPSS probability0.30%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Incorrect authorization in publish-mode endpoints in SiYuan before 3.7.4 allows remote attackers to read forbidden published documents. Eight reader-facing handlers in kernel/model/publish_access.go and inline graph and tag call sites use GetInvisiblePublishAccess, which enforces navigation visibility, instead of GetDisablePublishAccess, which is the check meant to block Disable=true notebooks and documents. No authentication or user interaction is required, but exposure is limited to content and metadata returned by publish-mode search, backlink, asset, criteria, recent-document, graph, and tag responses for items that remain Visible=true.

The record

CVE
CVE-2026-74906
Published
Aug 18, 2026
Updated
Aug 18, 2026
Vendor
SiYuan Note
Product
SiYuan
Classifications
CWE-863, T1213
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 18, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 18, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <3.7.4

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

SiYuan Note · SiYuanversion=0 <3.7.4

Published CVSS scores

7.5VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
8.7VulnCheckCVSS: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 describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-863Incorrect Authorization
T1213Data from Information Repositories

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo