CVE-2026-116171

waiting for further signals

GHSA-6gmc-424x-xgpm ↗EUVD-2026-109432 ↗

no check availablenot proven exploitable

cve.orgpublic poc−16dkev

siyuan-note siyuan >= 3.5.4, <= 3.8.6

fixed in v3.8.7

CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

ETK-2026-2601, permanent identifier

pkg:golang/siyuan-note/siyuan

cvss8.7cna vendorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

1h 08msince last run

27mAI analysis

timeline

0 = trigger signal

trigger signal +0dpublic poc+0dcve.org publication+16dwaiting for further signals

+5d

+10d

+15d

description

On Windows, SiYuan versions 3.5.4 through 3.8.6 can incorrectly allow access to protected local paths during Markdown import. An authenticated API caller may expose sensitive workspace files through assets served to other clients. Exploitation requires access to the affected import API on a vulnerable Windows deployment.

mitigation

Upgrade SiYuan to version 3.8.7 or later. Until upgraded, restrict authenticated access to the import API and limit exposure of served assets.

fixed in v3.8.7

check

exploit

automation

contextual

auth required

EPSS

–

agent run time

27m

cve.org record, t = 0

2026-10-25 13:20Z

Δ to public poc

−16d

Δ to kev

–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

2026-10-09 11:26Z
ghsa: trigger signal
https://github.com/siyuan-note/siyuan/security/advisories/GHSA-6gmc-424x-xgpm
2026-10-25 13:20Z
cve_org: trigger signal, started the run
https://www.cve.org/CVERecord?id=CVE-2026-116171

this entry in the feed

GET /api/v1/feed/CVE-2026-116171

{
  "etk_id": "ETK-2026-2601",
  "cve_id": "CVE-2026-116171",
  "display_id": "CVE-2026-116171",
  "ghsa_id": "GHSA-6gmc-424x-xgpm",
  "euvd_id": "EUVD-2026-109432",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Windows path validation bypass in SiYuan",
  "summary": "On Windows, SiYuan versions 3.5.4 through 3.8.6 can incorrectly allow access to protected local paths during Markdown import. An authenticated API caller may expose sensitive workspace files through assets served to other clients. Exploitation requires access to the affected import API on a vulnerable Windows deployment.",
  "mitigation": "Upgrade SiYuan to version 3.8.7 or later. Until upgraded, restrict authenticated access to the import API and limit exposure of served assets.",
  "vendor": "siyuan-note",
  "product": "siyuan",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.5.4, <= 3.8.6"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        "v3.8.7"
      ],
      "package_name": "siyuan-note/siyuan",
      "purl": "pkg:golang/siyuan-note/siyuan"
    }
  ],
  "cwes": [
    22
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 26.975320433333334,
  "t0_at": "2026-10-25T13:20:13.056000+00:00",
  "signals": {
    "public_poc": {
      "at": "2026-10-09T11:26:42+00:00",
      "days": -16.078831666666666,
      "is_lower_bound": false,
      "measured_at": "2026-10-25T13:20:13.056000+00:00",
      "url": "https://github.com/siyuan-note/siyuan/security/advisories/GHSA-6gmc-424x-xgpm"
    },
    "trigger_signal": {
      "at": "2026-10-09T11:26:42+00:00",
      "days": -16.078831666666666,
      "is_lower_bound": false,
      "measured_at": "2026-10-25T13:20:13.056000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-116171"
    }
  }
}

published 2026-10-25 13:28Z
last change 2026-10-25 18:20Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.