Why does GHSA-xxm9-w59q-m66x have no CVE ID yet?

GitHub Security Advisories published this advisory directly to customers before NVD assigned a CVE ID. This is the embargo-window disclosure pattern — vendors notify customers on day 0; NVD's public record follows days to weeks later.

What is the CVSS v3 score of GHSA-xxm9-w59q-m66x?

GHSA-xxm9-w59q-m66x has a CVSS v3 base score of 5.8, published by GitHub Security Advisories.

Which products are affected by GHSA-xxm9-w59q-m66x?

GHSA-xxm9-w59q-m66x affects 1 product, including: go/github.com/siyuan-note/siyuan/kernel:\u003c 3.7.4.

⚠ Withdrawn by GitHub Security Advisories

Withdrawn: October 1, 2026

GHSA-xxm9-w59q-m66xMediumCVSS 5.8Disclosed before NVD

Duplicate Advisory: getUniqueFilename passes an unvalidated client-supplied path to the filesystem, giving anonymous readers an existence oracle over the entire host filesystem

Vendor

GitHub Security Advisories

Published

August 13, 2026

Last Modified

October 1, 2026

📋 Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-hf8h-97gm-4x2p. This link is maintained to preserve external references.

Original Description

SiYuan versions before v3.7.4 contain a path traversal vulnerability in the getUniqueFilename endpoint that allows anonymous readers to probe filesystem existence without validation or confinement. Attackers can supply arbitrary absolute paths to determine whether files and directories exist on the host, enabling reconnaissance of the filesystem layout and installed software.

🎯 Affected products1

go/github.com/siyuan-note/siyuan/kernel:< 3.7.4

📋 Description

Duplicate Advisory

Original Description

🎯 Affected products1

🔗 References (4)