Information Disclosure in siyuan (CVE-2026-73047)
Summary
Vulnerability in siyuan (CVE-2026-73047). Confidential information can be exposed externally. Mitigation: upgrade to 3.7.4 or later.
Original description
The description as published by the source.
siyuan versions <= 3.7.3 (fixed in v3.7.4) contain a server-side template injection vulnerability in the attribute-view Template calculation feature (introduced in v3.7.0-beta.1). The feature's template engine uses Sprig's unmodified function map, which still exposes the env, expandenv, and getHostByName functions that were removed elsewhere for CVE-2024-55660. A local, unauthenticated attacker (the kernel binds to 127.0.0.1 by default with no per-UID access control) can inject a malicious Template calculation formula to read environment variables belonging to the account running siyuan — including from a separate, unprivileged OS account — and to perform DNS lookups from the server's network position.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-73047 has been found in siyuan.
Confidential information can be exposed externally. CVSS score: 6.2/10.
What to do: upgrade siyuan to 3.7.4 or later.
If unsure, ask your IT team or search "siyuan CVE-2026-73047" on the vendor's site.
CVE-2026-73047 (siyuan) — CWE-200 / CVSS v3 6.2
Attack vector: local / unauthenticated / no user interaction
Patched: 3.7.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in siyuan.
Check the vendor advisory for the affected versions of siyuan.
Severity: Medium (CVSS 6.2/10). Confidential information can be exposed externally.
Update to 3.7.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'siyuan' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'siyuan' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
siyuanを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade siyuan to 3.7.4ステージング環境で 3.7.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com