# CVE-2026-101092: SiYuan before v3.8.4 Information Disclosure via getCurrentAttrViewImages

> Attackers can leak image asset paths from unauthorized databases by bypassing publish-access checks in the getCurrentAttrViewImages endpoint.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-fg39-6m5r-264j, GHSA-j9p6-5639-gf4f

## What is CVE-2026-101092?

CVE-2026-101092 is a medium-severity vulnerability in siyuan-note siyuan, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SiYuan before v3.8.4 fails to enforce publish-access checks in the getCurrentAttrViewImages endpoint, allowing publish readers to retrieve image asset paths from unauthorized databases. Attackers can call the endpoint with an unrendered database identifier obtained through related endpoints to leak detached-row image asset paths and filenames that the rendering endpoint would deny.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-101092?


## How do I fix CVE-2026-101092?

No fix has been published for CVE-2026-101092 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-101092 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101092 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-101092 and fix it if it is affected.

What it is: CVE-2026-101092 is a medium-severity vulnerability in siyuan-note siyuan, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101092 exists.

Affected product: siyuan-note siyuan. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-101092/ (Markdown: https://insights.sbomify.com/CVE-2026-101092/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-101092
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-101092
- OSV: https://osv.dev/vulnerability/CVE-2026-101092

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-101092/
Summaries are generated and may contain mistakes; the official description above is the record.