GHSA-7P7C-PVVX-2VX3

GHSA-7P7C-PVVX-2VX3 is a medium-severity path traversal vulnerability in hyper-staticfile (rust), affecting versions < 0.9.2. It is fixed in 0.9.2, 0.10.0-alpha.2.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

hyper-staticfile's improper validation of Windows paths could lead to directory traversal attack

Path resolution in hyper-staticfile didn't correctly validate Windows paths, meaning paths like /foo/bar/c:/windows/web/screen/img101.png would be allowed and respond with the contents of c:/windows/web/screen/img101.png. Thus users could potentially read files anywhere on the filesystem.

This only impacts Windows. Linux and other unix likes are not impacted by this.

Impact

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.

Affected versions

hyper-staticfile (< 0.9.2) hyper-staticfile (= 0.10.0-alpha.1)

Security releases

hyper-staticfile → 0.9.2 (rust) hyper-staticfile → 0.10.0-alpha.2 (rust)

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

Upgrade the following packages to resolve this vulnerability:

hyper-staticfile to 0.9.2 or later; hyper-staticfile to 0.10.0-alpha.2 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is GHSA-7P7C-PVVX-2VX3? GHSA-7P7C-PVVX-2VX3 is a medium-severity path traversal vulnerability in hyper-staticfile (rust), affecting versions < 0.9.2. It is fixed in 0.9.2, 0.10.0-alpha.2. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
  2. Which versions of hyper-staticfile are affected by GHSA-7P7C-PVVX-2VX3? hyper-staticfile (rust) versions < 0.9.2 is affected.
  3. Is there a fix for GHSA-7P7C-PVVX-2VX3? Yes. GHSA-7P7C-PVVX-2VX3 is fixed in 0.9.2, 0.10.0-alpha.2. Upgrade to this version or later.
  4. Is GHSA-7P7C-PVVX-2VX3 exploitable, and should I be worried? Whether GHSA-7P7C-PVVX-2VX3 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
  5. What actually determines whether GHSA-7P7C-PVVX-2VX3 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.
  6. How do I fix GHSA-7P7C-PVVX-2VX3?
    • Upgrade hyper-staticfile to 0.9.2 or later
    • Upgrade hyper-staticfile to 0.10.0-alpha.2 or later

Other vulnerabilities in hyper-staticfile

Stop the waste.
Protect your environment with Kodem.