How severe is GHSA-jhmh-hr4g-c5g2?

No CVSS score has been assigned to GHSA-jhmh-hr4g-c5g2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jhmh-hr4g-c5g2?

Affected package information for GHSA-jhmh-hr4g-c5g2 is not yet fully mapped. Check the official advisory links for details.

How do I fix GHSA-jhmh-hr4g-c5g2?

Upgrade the affected component to the fixed release for GHSA-jhmh-hr4g-c5g2, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.

How do I detect GHSA-jhmh-hr4g-c5g2 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate GHSA-jhmh-hr4g-c5g2 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-jhmh-hr4g-c5g2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-jhmh-hr4g-c5g2 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-jhmh-hr4g-c5g2?

GHSA-jhmh-hr4g-c5g2 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th 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-jhmh-hr4g-c5g2?

GHSA-jhmh-hr4g-c5g2 is classified as CWE-73 (CWE-73). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-jhmh-hr4g-c5g2 published, and has it been updated?

GHSA-jhmh-hr4g-c5g2 was published on September 26, 2026 and was last updated on October 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

SiYuan before v3.8.4 Path Traversal via checkoutRepo…

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-jhmh-hr4g-c5g2.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

SiYuan versions before v3.8.4 contain a path traversal vulnerability in the checkoutRepo endpoint that allows authenticated administrators to write JSON files outside the workspace. Attackers can supply a sessionID parameter containing directory traversal sequences to overwrite arbitrary JSON files in pre-existing kernel-writable directories outside workspace boundaries.

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Fix
Upgrade the affected component to the fixed release for GHSA-jhmh-hr4g-c5g2, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

SiYuan versions before v3.8.4 contain a path traversal vulnerability in the checkoutRepo endpoint that allows authenticated administrators to write JSON files outside the workspace. Attackers can supply a sessionID parameter containing directory traversal sequences to overwrite arbitrary JSON files in pre-existing kernel-writable directories outside workspace boundaries.

O3 Security · Impact-Aware SCA

Is GHSA-jhmh-hr4g-c5g2 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

SiYuan before v3.8.4 Path Traversal via checkoutRepo sessionIDGHSA-jhmh-hr4g-c5g2