Summary
Yapscan's report receiver server vulnerable to path traversal and log injection
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.
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.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
GHSA-9H6H-9G78-86F7 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.19.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Vulnerable versions:
- v0.18.0
- v0.19.0 (unreleased)
This problem is patched in version v0.19.1
Frequently Asked Questions
- What is GHSA-9H6H-9G78-86F7? GHSA-9H6H-9G78-86F7 is a high-severity path traversal vulnerability in github.com/fkie-cad/yapscan (go), affecting versions >= 0.18.0, < 0.19.1. It is fixed in 0.19.1. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- How severe is GHSA-9H6H-9G78-86F7? GHSA-9H6H-9G78-86F7 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/fkie-cad/yapscan are affected by GHSA-9H6H-9G78-86F7? github.com/fkie-cad/yapscan (go) versions >= 0.18.0, < 0.19.1 is affected.
- Is there a fix for GHSA-9H6H-9G78-86F7? Yes. GHSA-9H6H-9G78-86F7 is fixed in 0.19.1. Upgrade to this version or later.
- Is GHSA-9H6H-9G78-86F7 exploitable, and should I be worried? Whether GHSA-9H6H-9G78-86F7 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-9H6H-9G78-86F7 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-9H6H-9G78-86F7? Upgrade
github.com/fkie-cad/yapscanto 0.19.1 or later.