Skip to main content
Menu
CVEs

SiYuan metadata disclosure in LAN sync before peer authentication

CVE-2026-134244Published November 21, 2026, updated

5.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 3.8.10
Who is exposed
Not reported

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

Original 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.

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.

“SiYuan 3.8.0 before 3.8.10 contains an information disclosure vulnerability in LAN sync”

vulncheck.com

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-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"}.

Affected versions

cve.now Index

15Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. Advisories don't say whether default setups are affected
  • Reach10/20Affects npm packages
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 37 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 5

Questions about CVE-2026-134244

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: cve.now feed data

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: github.com, vulncheck.com

Which versions are affected by CVE-2026-134244?

SiYuan (npm): from 3.8.0 before 3.8.10.

Source: cve.now feed data

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: github.com, vulncheck.com

How do I fix CVE-2026-134244?

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

Source: github.com, vulncheck.com

No corrections so far. Something wrong on this page? Report an error.