- Exploited
- No known exploitation
- Fix
- Fixed in 0.7.4
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.7.4.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
On Windows systems with 8.3 short file names, the actix-files crate can serve hidden files through their short-name aliases, letting a remote client read sensitive files such as `.env` or `.git/config` even when hidden file serving is disabled. Attackers could use this to expose secrets or source code.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
On Windows volumes with 8.3 short names, actix_files::Files can serve hidden files through their short-name aliases. The default path check rejects segments that start with a dot, but an alias such as ENV~1 or GIT~1 passes this check.
A remote client can read files such as .env or .git/config in the served directory even when use_hidden_files() is not enabled. This can expose secrets or source code.
Upgrade to actix-files 0.7.4 or later. As a workaround, remove sensitive files and directories from the served directory.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach10/20Affects crates.io packages
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.7.4.
Timeline
- Advisory published
- Record last updated
- First seen by cve.now
Affected versions
- actix-filescrates.io
From 0.0.0-0 · fixed in 0.7.4
Evidence 3
- Advisory
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about RUSTSEC-2026-0443
Is RUSTSEC-2026-0443 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by RUSTSEC-2026-0443?
actix-files (crates.io): from 0.0.0-0 before 0.7.4.Source: cve.now feed data
How do I fix RUSTSEC-2026-0443?
Upgrade to a fixed version: 0.7.4.Source: cve.now feed data