Quick answers
- Is CVE-2026-116168 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116168 being exploited in the wild.
- How severe is CVE-2026-116168?
- Medium severity, with a CVSS score of 6.2, published 25 October 2026.
- Which products and versions are affected?
- SiYuan Note SiYuan before 3.8.7.
- Is there a fix for CVE-2026-116168?
- Yes: fixed in 3.8.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116168 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-116168?
- Check whether you run SiYuan Note SiYuan at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 3.8.7
Technical details
The validateAssetUploadPaths function in the MCP asset tool uses an incomplete blacklist (isSensitivePath) to block uploads of sensitive files. The blacklist omits .env and .env.* files from its 17-entry dotfile list, allowing authenticated attackers to invoke the asset upload action with paths like /home/user/.env, copy the file into the workspace, and exfiltrate it via the /assets/ HTTP endpoint. This is a path traversal vulnerability (CWE-22) requiring MCP server access and an active agent principal but no additional filesystem privileges.
Affected products
- siyuan-note SiYuan before 3.8.7
Timeline
- 2026-10-09: disclosed
- 2026-10-25: advisory
- 2026-10-25: patched