GHSA-m3c2-496v-cw3v — v3
Fix: gofiber/fiber#4064GHSA-m3c2-496v-cw3v is a Path Traversal vulnerability in github.com/gofiber/fiber/v3. A fix is available for github.com/gofiber/fiber/v3 — see the affected versions and patch details below.
Fiber has an Arbitrary File Read in Static Middleware on Windows
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-m3c2-496v-cw3v.
EPSS Exploitation Probability
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
github.com/gofiber/fiber/v3Real-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
Summary
Description A Path Traversal (CWE-22) vulnerability in Fiber allows a remote attacker to bypass the static middleware sanitizer and read arbitrary files on the server file system on Windows. This affects Fiber v3 through version 3.0.0. This has been patched in Fiber v3 version 3.1.0.
Details
The vulnerability resides in middleware/static/static.go within the sanitizePath function. This function attempts to sanitize the requested path by checking for backslashes, decoding the URL, and then cleaning the path.
The vulnerability stems from two combined issues:
- The check for backslash characters happens before the URL decoding loop. If an attacker sends a double-encoded backslash, the initial check sees
%255Cand passes. The loop then decodes this into a single backslash. - The function uses
path.Cleanto clean the resulting string.path.Cleanis designed for slash-separated paths and does not recognize backslashes as directory separators. Consequently, sequences like..\..\are treated as valid filenames.
When this sanitized path is later used, the backslashes are interpreted as valid separators, allowing the attacker to traverse up the directory tree.
// pkg/static/static.go
func sanitizePath(p []byte, filesystem fs.FS) ([]byte, error) {
...
// this check happens BEFORE decoding
if bytes.IndexByte(p, '\\') >= 0 {
...
}
// This loop decodes %255C to %5C to \
for strings.IndexByte(s, '%') >= 0 {
us, err := url.PathUnescape(s)
...
s = us
}
// path.Clean only understands forward slashes (/)
s = pathpkg.Clean("/" + s)
...
return utils.UnsafeBytes(s), nil
}
Impact
This impacts Fiber v3 prereleases through stable release version 3.0.0.
Successful exploitation requires the server to be using the static middleware on Windows, as this is the only OS where backslashes are treated as directory separators by the file system.
Exploitation allows directory traversal on the host server. An attacker can read arbitrary files within the scope of the application server context. Depending on permissions and deployment conditions, attackers may access sensitive files outside the web root, such as configuration files, source code, or system files. Leaking application secrets often leads to further compromise.
Patches
This has been patched in Fiber v3 version 3.1.0. Users are strongly encouraged to update to the latest available release.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/gofiber/fiber/v3 | all versions | 3.1.0go get github.com/gofiber/fiber/v3@v3.1.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/gofiber/fiber/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/gofiber/fiber/v3 to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m3c2-496v-cw3v 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-m3c2-496v-cw3v can be triaged on real exposure rather than presence alone.
Tailored to GHSA-m3c2-496v-cw3v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-m3c2-496v-cw3v in your dependencies?
O3 Security finds GHSA-m3c2-496v-cw3v across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.