Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Informational severity, published 6 November 2026.
- Which products and versions are affected?
- Actix-Files before 0.7.4; actix-files (crates.io) SEMVER:introduced=0.0.0-0,fixed=0.7.4.
- Is there a fix for This vulnerability?
- Yes. actix-files (crates.io): upgrade to 0.7.4 or later. Until then: As a workaround, remove sensitive files and directories (such as .env and .git) from the served directory. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network.
- Am I affected?
- Check whether you run Actix-Files or actix-files (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- actix-files (crates.io): upgrade to 0.7.4 or later
cargo update -p actix-files
As a workaround, remove sensitive files and directories (such as .env and .git) from the served directory.
Technical details
The vulnerability is a path traversal bypass in actix-files' default path validation on Windows. The library checks for and rejects path segments starting with a dot, but Windows 8.3 short-name aliases circumvent this check. A remote, unauthenticated attacker can request hidden files through their aliases to retrieve secrets and source code; the fix exists in version 0.7.4 and later.
Affected products
- Actix actix-files before 0.7.4
Identifiers
- GHSA-8hcm-m7r7-frwc
- RUSTSEC-2026-0443
Timeline
- 2026-11-06: disclosed
- 2026-11-06: patched