CVE-2026-57581
MediumCVSS 5.3Summary
DotVVM prior to versions 4.2.11, 4.3.15, and 5.0.0-preview09-final allows unauthenticated users to submit files directly to DotvvmFileUploadMiddleware without an X-DotVVM-UploadToken generated by the FileUpload component. An attacker can repeatedly upload files and fill application storage, causing denial of service. DotvvmConfiguration.Security.AuthorizeFileUpload can additionally restrict which users may upload files.
Risk Assessment
The vulnerability enables a remote denial-of-service attack by filling application storage with unwanted files, potentially leading to service unavailability.
Recommendation
It is recommended to upgrade DotVVM to version 4.2.11, 4.3.15, or 5.0.0-preview09-final or later, and enable the AuthorizeFileUpload option to restrict file upload access.
Other vulnerabilities in DotVVM
See all- CVE-2026-57577High
In DotVVM prior to 4.2.11, 4.3.15, and 5.0.0-preview09-final, a route with multiple unconstrained parameters in one path segment can cause excessive regex backtracking in DotvvmRoute.IsMatch when a long near-match path is supplied. The lack of a matching timeout in DotvvmRouteParser.RouteRegex leads to resource exhaustion.
- CVE-2026-57578Critical
DotVVM is an open source MVVM framework for web applications. Prior to 4.2.11, 4.3.15, and 5.0.0-preview09-final, AuthorizeActionFilter performs no authorization because its explicit ICommandActionFilter.OnCommandExecutingAsync, IViewModelActionFilter.OnViewModelCreatedAsync, and IPresenterActionFilter.OnPresenterExecutingAsync implementations return completed tasks instead of invoking the corresponding checks. Applications relying on this filter can therefore expose protected commands, view models, or presenters to unauthorized requests without any special bypass technique.
Original NVD description (English source)
DotVVM is an open source MVVM framework for web applications. Prior to 4.2.11, 4.3.15, and 5.0.0-preview09-final, applications with configured file upload storage allow unauthenticated users to submit files directly to DotvvmFileUploadMiddleware without an X-DotVVM-UploadToken generated by the FileUpload component. An attacker can repeatedly upload files and fill application storage, causing denial of service. DotvvmConfiguration.Security.AuthorizeFileUpload can additionally restrict which users may upload files. This issue is fixed in versions 4.2.11, 4.3.15, and 5.0.0-preview09-final.