How severe is GHSA-fqj6-whhx-47p7?

No CVSS score has been assigned to GHSA-fqj6-whhx-47p7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fqj6-whhx-47p7?

GHSA-fqj6-whhx-47p7 affects the following packages: github.com/siyuan-note/siyuan/kernel (Go). Ecosystems affected: Go.

How do I fix GHSA-fqj6-whhx-47p7?

No patched version of github.com/siyuan-note/siyuan/kernel has shipped for GHSA-fqj6-whhx-47p7 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-fqj6-whhx-47p7 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/siyuan-note/siyuan/kernel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-fqj6-whhx-47p7 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-fqj6-whhx-47p7?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-fqj6-whhx-47p7 can be triaged on real exposure rather than presence alone.

Is GHSA-fqj6-whhx-47p7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-fqj6-whhx-47p7 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-fqj6-whhx-47p7?

GHSA-fqj6-whhx-47p7 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 29th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-fqj6-whhx-47p7?

GHSA-fqj6-whhx-47p7 is classified as Path Traversal (CWE-22), Cross-site Scripting (XSS) (CWE-79). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-fqj6-whhx-47p7 published, and has it been updated?

GHSA-fqj6-whhx-47p7 was published on December 11, 2024 and was last updated on December 12, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-fqj6-whhx-47p7 — kernel

Fix: siyuan-note/siyuan@e70ed57

GHSA-fqj6-whhx-47p7 is a Path Traversal vulnerability in github.com/siyuan-note/siyuan/kernel. No vendor fix is recorded yet; mitigation options are listed below.

SiYuan has an arbitrary file write in the host via /api/asset/upload

Also known asCVE-2024-55659GO-2024-3326

Published

Dec 11, 2024

Updated

Dec 12, 2024

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Sep 25, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-fqj6-whhx-47p7.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs29th percentile — riskier than 29% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐹github.com/siyuan-note/siyuan/kernel

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

SiYuan is a personal knowledge management system. Prior to version 3.1.16, the /api/asset/upload endpoint in Siyuan is vulnerable to both arbitrary file write to the host and stored cross-site scripting (via the file write). Version 3.1.16 contains a patch for the issue.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/siyuan-note/siyuan/kernel`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/siyuan-note/siyuan/kernel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of github.com/siyuan-note/siyuan/kernel has shipped for GHSA-fqj6-whhx-47p7 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-fqj6-whhx-47p7 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-fqj6-whhx-47p7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary The /api/asset/upload endpoint in Siyuan is vulnerable to both arbitrary file write to the host and stored XSS (via the file write). ### Impact Arbitrary file write

O3 Security · Impact-Aware SCA

Is GHSA-fqj6-whhx-47p7 in your dependencies?

O3 Security finds GHSA-fqj6-whhx-47p7 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works