ETK-2026-3829Zero's internal tracking ID, independent of the CVE number.

waiting for further signalsZero needs more public information before it can validate it.

GHSA-xxqp-6jxw-qr84 ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−1.8dkevAttacks confirmed in the real world.
go:github.com/siyuan-note/siyuan/kernel v3.8.8
fixed in v3.8.10
CWE-863 Incorrect Authorization
ETK-2026-3829Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:golang/github.com/siyuan-note/siyuan/kernel
12h 26msince last run
16mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0dpublic poc+0dwaiting for further signals+1.3d
0
+1d
+2d

description

SiYuan kernel versions before v3.8.10 can authorize an asset using a different published document than the one that owns the file. On public-publish deployments without Basic Auth, an unauthenticated visitor may read a password-protected asset when documents share an asset path and resolution selects the protected file; with Basic Auth enabled, a Reader account is required.

mitigation

Upgrade github.com/siyuan-note/siyuan/kernel to v3.8.10 or later. Until upgraded, disable public publishing or require Basic Auth to reduce unauthenticated exposure.

fixed in v3.8.10

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
−1.8d
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-06 05:42Z
  2. 2026-11-06 05:42Z

this entry in the feed

GET /api/v1/feed/ETK-2026-3829

{
  "etk_id": "ETK-2026-3829",
  "cve_id": null,
  "display_id": "ETK-2026-3829",
  "ghsa_id": "GHSA-xxqp-6jxw-qr84",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Cross-document asset authorization flaw in SiYuan kernel",
  "summary": "SiYuan kernel versions before v3.8.10 can authorize an asset using a different published document than the one that owns the file. On public-publish deployments without Basic Auth, an unauthenticated visitor may read a password-protected asset when documents share an asset path and resolution selects the protected file; with Basic Auth enabled, a Reader account is required.",
  "mitigation": "Upgrade github.com/siyuan-note/siyuan/kernel to v3.8.10 or later. Until upgraded, disable public publishing or require Basic Auth to reduce unauthenticated exposure.",
  "vendor": "go",
  "product": "go:github.com/siyuan-note/siyuan/kernel",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "v3.8.8"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        "v3.8.10"
      ],
      "package_name": "github.com/siyuan-note/siyuan/kernel",
      "purl": "pkg:golang/github.com/siyuan-note/siyuan/kernel"
    }
  ],
  "cwes": [
    863
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 15.573459983333333,
  "t0_at": null,
  "signals": {
    "public_poc": {
      "at": "2026-11-06T05:42:26+00:00",
      "days": -1.7976535621875,
      "is_lower_bound": true,
      "measured_at": "2026-11-08T00:51:03.304601+00:00",
      "url": "https://github.com/siyuan-note/siyuan/security/advisories/GHSA-xxqp-6jxw-qr84"
    },
    "trigger_signal": {
      "at": "2026-11-06T05:42:26+00:00",
      "days": -1.7976535621875,
      "is_lower_bound": true,
      "measured_at": "2026-11-08T00:51:03.304601+00:00",
      "url": "https://github.com/siyuan-note/siyuan/security/advisories/GHSA-xxqp-6jxw-qr84"
    }
  }
}

published 2026-11-07 12:12Z
last change 2026-11-08 00:40Z

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.