actix-files has a possible exposure of information vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary When passing a non-existing folder to the actixfiles::Files::new() method causes the actix server to expose unexpected files. Details The actix-files library exposes a Files struct that configures an actix service to serve the files in a folder as static assets. Below you can find the signature of the Files::new method: When the mountpath you pass to Files doesn't exist, it defaults to an empty path (Path::new()). When the service receives a HTTP request, it joins the request information with the empty path and calls canonicalize. Rust resolves this path as relative and returns any file that matches it. This behavior causes the library to expose unexpected files when the folder is not present. PoC There is a working PoC on https://github.com/Angelmmiguel/actix-files-vuln, although the next steps can be followed to reproduce the issue 1. Clone the https://github.com/actix/examples repository. 2. Change your directory to the basics/static-files folder. 3. Edit the src/main.rs…

Published by the source

6 Feb 2026, 18:56 UTC

Last modified by the source

6 Feb 2026, 18:56 UTC

Source last checked

26 Oct 2026, 15:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8v2v-wjwg-vx6r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-8v2v-wjwg-vx6r

Advisory: actix-files has a possible exposure of information vulnerability
IDs: GHSA-8v2v-wjwg-vx6r
Record: https://patchnext.com/advisories/ghsa-8v2v-wjwg-vx6r (revision 1, source checked 26 Oct 2026, 15:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: actix-files 0.6.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io actix-files: affected <= 0.6.9; fixed in 0.6.10

## Suggested inspection (read-only)
- crates.io actix-files: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on actix-files.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8v2v-wjwg-vx6r (GitHub-reviewed advisory GHSA-8v2v-wjwg-vx6r lists affected ranges: crates.io actix-files >=0 <=0.6.9)

Commands are suggestions: review each one before running it.