How severe is GHSA-x8qh-7475-c5mp?

No CVSS score has been assigned to GHSA-x8qh-7475-c5mp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-x8qh-7475-c5mp?

GHSA-x8qh-7475-c5mp affects the following packages: github.com/drakkan/sftpgo/v2 (Go), github.com/drakkan/sftpgo (Go). Ecosystems affected: Go.

How do I fix GHSA-x8qh-7475-c5mp?

Update github.com/drakkan/sftpgo/v2 to 2.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x8qh-7475-c5mp is resolved across your whole dependency graph.

How do I detect GHSA-x8qh-7475-c5mp in my Go dependencies?

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

How do I mitigate GHSA-x8qh-7475-c5mp 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-x8qh-7475-c5mp?

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

Is GHSA-x8qh-7475-c5mp actively exploited in the wild?

No public exploit code has been indexed for GHSA-x8qh-7475-c5mp 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-x8qh-7475-c5mp?

GHSA-x8qh-7475-c5mp has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 43th 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-x8qh-7475-c5mp?

GHSA-x8qh-7475-c5mp is classified as Path Traversal (CWE-22). This weakness type 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-x8qh-7475-c5mp published, and has it been updated?

GHSA-x8qh-7475-c5mp was published on March 13, 2026 and was last updated on March 24, 2026. 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-x8qh-7475-c5mp — v2

Fix: drakkan/sftpgo@2f092d1

GHSA-x8qh-7475-c5mp is a Path Traversal vulnerability in github.com/drakkan/sftpgo/v2. A fix is available for github.com/drakkan/sftpgo/v2 — see the affected versions and patch details below.

SFTPGo Vulnerable to Path Traversal and Permission Bypass via Path Normalization Discrepancy

Also known asCVE-2026-30914GO-2026-4699

Published

Mar 13, 2026

Updated

Mar 24, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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-x8qh-7475-c5mp.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs43th percentile — riskier than 43% 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

2 pkgs affected

🐹github.com/drakkan/sftpgo/v2🐹github.com/drakkan/sftpgo

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

Impact

In SFTPGo versions prior to 2.7.1, a path normalization discrepancy between the protocol handlers and the internal Virtual Filesystem routing can lead to an authorization bypass. An authenticated attacker can craft specific file paths to bypass folder-level permissions or escape the boundaries of a configured Virtual Folder.

Patches

This issue has been addressed in SFTPGo version 2.7.1. The fix introduces strict edge-level path normalization, ensuring that all protocol inputs are fully sanitized and resolved to canonical POSIX paths before any routing or permission evaluations occur.

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/drakkan/sftpgo/v2`	all versions	2.7.1`go get github.com/drakkan/sftpgo/v2@v2.7.1`
🐹Go	`github.com/drakkan/sftpgo`	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/drakkan/sftpgo/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/drakkan/sftpgo/v2 to 2.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x8qh-7475-c5mp is resolved across your whole dependency graph.
Workarounds
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-x8qh-7475-c5mp can be triaged on real exposure rather than presence alone.

Tailored to GHSA-x8qh-7475-c5mp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact In SFTPGo versions prior to 2.7.1, a path normalization discrepancy between the protocol handlers and the internal Virtual Filesystem routing can lead to an authorization bypass. An authenticated attacker can craft specific file paths to bypass folder-level permissions or escape the boundaries of a configured Virtual Folder. ### Patches This issue has been addressed in SFTPGo version 2.7.1. The fix introduces strict edge-level path normalization, ensuring that all protocol inputs are fully sanitized and resolved to canonical POSIX paths before any routing or permission evaluatio

O3 Security · Impact-Aware SCA

Is GHSA-x8qh-7475-c5mp in your dependencies?

O3 Security finds GHSA-x8qh-7475-c5mp 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