CVE-2026-72814: actix-files has a possible exposure of information vulnerability

CVE-2026-72814 · Severity: medium · CVSS 4 · Published 2026-08-14

The actix-files crate (actix_files) before version 0.6.10 contains an information exposure vulnerability. When a non-existing folder is passed as the serve_from argument to Files::new(), the mount path defaults to an empty path; the service then joins the request path with this empty path and canonicalizes it, causing Rust to resolve it as a relative path. As a result, an attacker can request paths that resolve relative to the application's working directory and access unintended files.

Technologies: actix-files (crates.io). Vendors: crates.io.

Quick answers

Is CVE-2026-72814 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-72814 being exploited in the wild.
How severe is CVE-2026-72814?
Medium severity, with a CVSS score of 4, published 14 August 2026.
Which products and versions are affected?
actix-files (crates.io) SEMVER:introduced=0,fixed=0.6.10.
Is there a fix for CVE-2026-72814?
Yes. actix-files (crates.io): upgrade to 0.6.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-72814?
Check whether you run 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.6.10 or later
    cargo update -p actix-files

Affected products

  • actix-files (crates.io) SEMVER:introduced=0,fixed=0.6.10

Identifiers

  • CVE-2026-72814
  • GHSA-8v2v-wjwg-vx6r

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.