Skip to main content
Menu
CVEs

Actix Files hidden file disclosure in static file handler

Affects actix-files before 0.7.4 when served on Windows with actix_files::Files, where NTFS 8.3 short names expose hidden files such as .env and .git contents. Fixed in 0.7.4.

CVE-2026-134347Published November 21, 2026, updated

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 0.7.4
Who is exposed
Default setups

Summary

Written by a model

actix-files before 0.7.4 contains an information disclosure vulnerability that allows remote unauthenticated attackers to read hidden files by requesting Windows 8.3 short-name aliases. Attackers can request short names like ENV~1 or GIT~1/config to bypass the leading-dot check in actix_files::Files and retrieve .env secrets and .git contents.

Who should check

Teams running actix-files before 0.7.4 on Windows that serve a directory with actix_files::Files, including static file servers.

“Applications serving a directory with actix_files::Files on Windows”

github.com

What to do

  1. Check every install: default setups are affected.

  2. Upgrade to a fixed version: 0.7.4.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134347 (actix-files before 0.7.4 Hidden File Disclosure via Windows 8.3 Short Names), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134347 (entry last updated 2026-11-21):
Affected:
- crates.io package actix-files: fixed in 0.7.4
Fixed versions: 0.7.4.
Conditions (all must be true for the bug to be hit):
- Runs actix-files before 0.7.4. (source: https://www.vulncheck.com/advisories/actix-files-before-0.7.4-hidden-file-disclosure-via-windows-8.3-short-names)
- Server runs on Windows, where NTFS assigns 8.3 short names. (source: https://github.com/actix/actix-web/security/advisories/GHSA-8hcm-m7r7-frwc)
- Serves a directory with actix_files::Files. (source: https://github.com/actix/actix-web/security/advisories/GHSA-8hcm-m7r7-frwc)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-134347 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134347 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (crates.io): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/actix/actix-web/security/advisories/GHSA-8hcm-m7r7-frwc
- https://www.vulncheck.com/advisories/actix-files-before-0.7.4-hidden-file-disclosure-via-windows-8.3-short-names
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134347
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134347"}.

Affected versions

cve.now Index

43Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure22/25Default setups, reachable over the network without a login
  • Reach12/20actix-files: 122K downloads a week
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 83 if added to CISA KEV
  • Would score about 78 if CISA's SSVC rates exploitation active

Impact

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · actix/actix-web · Advisory GHSA-8hcm-m7r7-frwc
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134347
RecordNVD · CVE-2026-134347
Other links 1
Linkvulncheck.com · advisories/actix-files-before-0.7.4-hidden-file-disclosure-via-windows-8.3-short-names

Questions about CVE-2026-134347

Is CVE-2026-134347 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

What does this mean?

Remote clients can read hidden files that the default configuration is meant to hide, such as .env secrets and .git contents including .git/config, without authentication.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134347?

actix-files (crates.io): before 0.7.4.

Source: cve.now feed data

Am I affected, and how do I check?

Versions of actix-files before 0.7.4 are affected, but only when the server runs on Windows, where NTFS assigns 8.3 short names, and the application serves a directory with actix_files::Files. To check, look at the actix-files version in Cargo.lock and confirm whether the server runs on Windows.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134347?

Upgrade actix-files to 0.7.4, the fixed version.

Source: vulncheck.com, github.com

No corrections so far. Something wrong on this page? Report an error.