CVE-2026-69085

validatedZero produced an exploit or a check.

GHSA-33jq-p8c2-q3q4 ↗EUVD-2026-52278 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+59dkevAttacks confirmed in the real world.
go:github.com/siyuan-note/siyuan/kernel < 0.0.0-20260721043339-eef10568384e
fixed in 0.0.0-20260721043339-eef10568384e
ETK-2026-248, permanent identifier
pkg:golang/github.com/siyuan-note/siyuan/kernel
+60dTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
cve.org publication−59dtrigger signal +0dpublic poc+0dcheck available+0.5dagent stopped
−40d
−20d

description

SiYuan kernel document search is vulnerable to SQL injection through a caller-controlled search keyword. An attacker who can reach the publish search endpoint, including anonymously when publish authentication is disabled, can read or alter data in cleartext notebooks; encrypted notebooks are outside the affected database scope.

mitigation

Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260721043339-eef10568384e or later. Until upgraded, disable public or anonymous publish access and restrict publish reader tokens.

fixed in 0.0.0-20260721043339-eef10568384e

check
available
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.
deterministic
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.
1.5%73rd percentile
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-08-03 13:20Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+59d
Δ to kevAttacks confirmed in the real world.
–

outcome

Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.

source signals

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

  1. 2026-08-03 13:20Z
  2. 2026-10-01 14:38Z
    ghsa: trigger signal, started the run
  3. 2026-10-01 14:38Z
  4. 2026-10-02 01:46Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-248",
  "cve_id": "CVE-2026-69085",
  "display_id": "CVE-2026-69085",
  "ghsa_id": "GHSA-33jq-p8c2-q3q4",
  "euvd_id": "EUVD-2026-52278",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in SiYuan kernel document search",
  "summary": "SiYuan kernel document search is vulnerable to SQL injection through a caller-controlled search keyword. An attacker who can reach the publish search endpoint, including anonymously when publish authentication is disabled, can read or alter data in cleartext notebooks; encrypted notebooks are outside the affected database scope.",
  "mitigation": "Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260721043339-eef10568384e or later. Until upgraded, disable public or anonymous publish access and restrict publish reader tokens.",
  "vendor": "go",
  "product": "go:github.com/siyuan-note/siyuan/kernel",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 0.0.0-20260721043339-eef10568384e"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        "0.0.0-20260721043339-eef10568384e"
      ],
      "package_name": "github.com/siyuan-note/siyuan/kernel",
      "purl": "pkg:golang/github.com/siyuan-note/siyuan/kernel"
    }
  ],
  "cwes": null,
  "cvss_score": 10,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N",
  "epss_score": 0.0149,
  "epss_percentile": 0.7371,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.016127933333333334,
  "t0_at": "2026-08-03T13:20:40.650000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-02T01:46:22.265091+00:00",
      "days": 59.517842767256944,
      "is_lower_bound": false,
      "measured_at": "2026-08-03T13:20:40.650000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-10-01T14:38:48+00:00",
      "days": 59.05425173611111,
      "is_lower_bound": false,
      "measured_at": "2026-08-03T13:20:40.650000+00:00",
      "url": "https://github.com/advisories/GHSA-33jq-p8c2-q3q4"
    },
    "trigger_signal": {
      "at": "2026-10-01T14:38:48+00:00",
      "days": 59.05425173611111,
      "is_lower_bound": false,
      "measured_at": "2026-08-03T13:20:40.650000+00:00",
      "url": "https://github.com/advisories/GHSA-33jq-p8c2-q3q4"
    }
  }
}

published 2026-10-01 15:27Z
last change 2026-10-21 07:48Z

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.