Skip to main content
VulnerabilityPublished Updated

CVE-2026-101092: siyuan · Information Exposure

Affects siyuanSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 3.8.4 when convenient.

Data as of 11 Nov 2026, 23:24 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.8.4
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

What to do

Upgrade siyuan and siyuan-note/siyuan to 3.8.4.

Affected software

ProductAffectedFixed in
siyuan-notesiyuanAffected
  • <3.8.4
Fixed in
  • 3.8.4
GitHubsiyuan-note/siyuanpkg:github/siyuan-note/siyuanOther threatsAffected
  • <3.8.4
Fixed in
  • 3.8.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade SiYuan to version 3.8.4 or later, where this access control issue has been fixed. Since the vulnerability affects versions before 3.8.4, applying the official update is the recommended remediation. No temporary workarounds or mitigations are indicated.

Description

CVE-2026-101092 is a medium severity vulnerability in SiYuan note-taking software versions before 3.8.4. The issue involves a failure to enforce publish-access checks in the getCurrentAttrViewImages endpoint, allowing unauthorized users with publish reader access to retrieve image asset paths from databases they should not access. This can lead to exposure of sensitive image asset paths and filenames that the rendering endpoint would normally block.

References

Community reviews

Loading reviews…