Process crash via unchecked empty range vector
Published Aug 14, 2026 · Updated Aug 14, 2026
Denial of service in actix-files before 0.6.10 allows remote attackers to crash an Actix Web process via an empty Range header. The static-file response path indexes the first element returned by HttpRange::parse even though parsing an empty header returns an empty vector, causing a panic in named.rs. A process-wide crash requires a build configured to abort on panic; the default unwind behavior closes the affected connection and replaces the worker.
Summary
What happened
Denial of service in actix-files before 0.6.10 allows remote attackers to crash an Actix Web process via an empty Range header. The static-file response path indexes the first element returned by HttpRange::parse even though parsing an empty header returns an empty vector, causing a panic in named.rs. A process-wide crash requires a build configured to abort on panic; the default unwind behavior closes the affected connection and replaces the worker.
The record
- CVE
- CVE-2026-72813
- Published
- Aug 14, 2026
- Updated
- Aug 14, 2026
- Vendor
- Actix
- Product
- Actix Web
- Classifications
- CWE-248, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 14, 2026CVE publishedPublication date reported by the CVE source.
- Aug 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.6.10
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Actix advisory minimal reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo