GHSA-9h6h-9g78-86f7 is a high-severity (CVSS 7.5) vulnerability in github.com/fkie-cad/yapscan. A fix is available for github.com/fkie-cad/yapscan — see the affected versions and patch details below.
Yapscan's report receiver server vulnerable to path traversal and log injection
Real-World Exposure
github.com/fkie-cad/yapscanReal-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
If you make use of the report receiver server (experimental), a client may be able to forge requests such that arbitrary files on the host can be overwritten (subject to permissions of the yapscan server), leading to loss of data. This is particularly problematic if you do not authenticate clients and/or run the server with elevated permissions.
Patches
Vulnerable versions:
- v0.18.0
- v0.19.0 (unreleased)
This problem is patched in version v0.19.1
Workarounds
Update to the newer version is highly encouraged!
Measures to reduce the risk of this include authenticating clients (see --client-ca flag) and containerization of the yapscan server.
References
The tracking issue is #35. There you can find the commits, fixing the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/fkie-cad/yapscan | ≥ 0.18.0&&< 0.19.1 | 0.19.1go get github.com/fkie-cad/yapscan@v0.19.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/fkie-cad/yapscan, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/fkie-cad/yapscan to 0.19.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9h6h-9g78-86f7 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-9h6h-9g78-86f7 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-9h6h-9g78-86f7. 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-9h6h-9g78-86f7 in your dependencies?
O3 Security finds GHSA-9h6h-9g78-86f7 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.