SiYuan authentication bypass in history route
Only affects SiYuan before 3.8.10 behind a publicly reachable loopback reverse proxy that preserves Host, does not overwrite X-Forwarded-For, and has no lock-screen password. Fixed in 3.8.10.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.8.10
- Who is exposed
- Not reported
Summary
SiYuan has an authentication bypass that lets a remote attacker, without logging in, gain the Administrator role by spoofing the X-Forwarded-For header through a reverse proxy that trusts loopback addresses. The attacker can also read private note-history contents through the history route when no lock-screen password is set.
Written by a model
Original description
SiYuan before 3.8.10 contains an authentication bypass vulnerability that allows unauthenticated attackers to gain Administrator role by spoofing X-Forwarded-For through a loopback-trusted reverse proxy. Attackers can send requests with Host set to localhost and X-Forwarded-For set to 127.0.0.1 to read private note-history contents via the /history/*path route when no lock-screen password is set.
Who should check
Teams running SiYuan Note (siyuan) before 3.8.10 behind a reverse proxy that trusts loopback addresses, with no lock-screen password set.
“Affecting siyuan < 3.8.10”
What to do
Upgrade to a fixed version: 3.8.10.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134249 (SiYuan before 3.8.10 Authentication Bypass via X-Forwarded-For on History Route), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-134249 (entry last updated 2026-11-21):
Affected:
- siyuan-note siyuan: fixed in 3.8.10
Fixed versions: 3.8.10.
Conditions (all must be true for the bug to be hit):
- SiYuan before 3.8.10. (source: https://www.vulncheck.com/advisories/siyuan-before-3.8.10-authentication-bypass-via-x-forwarded-for-on-history-route)
- Reached through a loopback-trusted reverse proxy that preserves the Host header and does not overwrite X-Forwarded-For. (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-gmcm-mggw-8759)
- No lock-screen password is set. (source: https://www.vulncheck.com/advisories/siyuan-before-3.8.10-authentication-bypass-via-x-forwarded-for-on-history-route)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-134249 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134249 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/siyuan-note/siyuan/security/advisories/GHSA-gmcm-mggw-8759
- https://github.com/siyuan-note/siyuan/commit/f951019168faf035b36c98f8e672719d511881ac
- https://www.vulncheck.com/advisories/siyuan-before-3.8.10-authentication-bypass-via-x-forwarded-for-on-history-route
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-134249
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134249"}.Affected versions
- siyuan-note siyuanfixed in 3.8.10
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · siyuan-note/siyuan · Advisory GHSA-gmcm-mggw-8759 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134249 |
| Record | NVD · CVE-2026-134249 |
| Other links 2 | |
| Patch | GitHub · siyuan-note/siyuan · Commit f9510191 |
| Link | vulncheck.com · advisories/siyuan-before-3.8.10-authentication-bypass-via-x-forwarded-for-on-history-route |
Questions about CVE-2026-134249
Is CVE-2026-134249 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A request arriving through a loopback-trusted reverse proxy can be treated as coming from a local Administrator without logging in. An unauthenticated remote caller can then read private note-history contents.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134249?
siyuan: before 3.8.10.
Source: cve.now feed data
Am I affected, and how do I check?
Versions of SiYuan before 3.8.10 are affected, but only in deployments where a publicly reachable loopback reverse proxy preserves the Host header, does not overwrite X-Forwarded-For, and has no lock-screen password set. Check your SiYuan version and whether a lock-screen password is configured to see which of these apply to your setup.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134249?
Upgrade SiYuan to version 3.8.10 or later, which is the fixed version.
Source: vulncheck.com, github.com
Related
- CVE-2026-130682SiYuan before 3.8.10 Stored XSS to RCE via Table Caption
- CVE-2026-130681SiYuan before 3.8.10 Stored XSS to RCE via Attribute View Name
- CVE-2026-130680SiYuan 3.3.0 before 3.8.10 Stored XSS to RCE via AttributeView Checkbox Column
- CVE-2026-130678SiYuan before 3.8.10 Stored XSS to RCE via Attribute View Column Name
- CVE-2026-130679SiYuan before 3.8.10 Stored XSS to RCE via Attribute View Asset Image src
- CVE-2026-130683SiYuan before 3.8.10 Path Traversal via /api/file/copyFile Deny-List Bypass
No corrections so far. Something wrong on this page? Report an error.