Skip to content

← Actionable
High, CVSS 7.7amended

SiYuan: Path Traversal via unvalidated avID in RenderAttributeView/AV read endpoints : reader-reachable cross-scope attribute-view disclosure

CVE-2026-69086GHSA-7hm9-v7vf-7g4w

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/siyuan-note/siyuan/kernel 0.0.0-20260720151813-0f5a0e7c67b0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS
  • CVE-2026-69086: 0.53% estimated exploitation activity in the next 30 days; percentile 45.00 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

CVE: This vulnerability corresponds to CVE-2026-69086. Summary Four attribute-view read endpoints build a filesystem path from a caller-controlled id/avID and read it without confining the result to the attribute-view storage directory (DataDir/storage/av/). On the load (file-exists) code path there is no boundary check, so an avID containing ../ segments escapes storage/av/ and causes the kernel to read a .json file elsewhere in the workspace. The endpoints require only CheckAuth, which the publish service's RoleReader token satisfies; when Publish.Auth.Enable is false the publish proxy uses the anonymous account, making the surface reachable with no credentials. Details Affected endpoints (all gated by CheckAuth only, no CheckAdminRole): - POST /api/av/renderAttributeView  → arg["id"] - POST /api/av/getAttributeViewKeysByID → arg["avID"] - POST /api/av/getAttributeViewKeys  → arg["id"] - POST /api/av/getCurrentAttrViewImages → arg["id"] In model.RenderAttributeView…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-7hm9-v7vf-7g4w

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6373

  3. Revision 1 · created ·

    Published from osv record GHSA-7hm9-v7vf-7g4w

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-69086

Advisory: SiYuan: Path Traversal via unvalidated avID in RenderAttributeView/AV read endpoints : reader-reachable cross-scope attribute-view disclosure
IDs: CVE-2026-69086, GHSA-7hm9-v7vf-7g4w
Record: https://patchnext.com/advisories/cve-2026-69086 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/siyuan-note/siyuan/kernel 0.0.0-20260720151813-0f5a0e7c67b0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260720151813-0f5a0e7c67b0; fixed in 0.0.0-20260720151813-0f5a0e7c67b0

## Suggested inspection (read-only)
- Go github.com/siyuan-note/siyuan/kernel: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/siyuan-note/siyuan/kernel.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-7hm9-v7vf-7g4w (OSV record GHSA-7hm9-v7vf-7g4w lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260720151813-0f5a0e7c67b0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6373 (OSV record GO-2026-6373 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260720151813-0f5a0e7c67b0 (fixed))
- Verified: https://github.com/advisories/GHSA-7hm9-v7vf-7g4w (GitHub-reviewed advisory GHSA-7hm9-v7vf-7g4w lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260720151813-0f5a0e7c67b0)

Commands are suggestions: review each one before running it.

Loading voting…