CVE-2026-57577
HighCVSS 8.2Summary
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.
Risk Assessment
A remote attacker can send crafted requests causing high CPU usage and potential application paralysis (denial of service).
Recommendation
Upgrade DotVVM to 4.2.11, 4.3.15, or 5.0.0-preview09-final, which introduce a timeout and non-backtracking engine.
Other vulnerabilities in DotVVM
See all- CVE-2026-57581Medium
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.
- 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, a route containing multiple unconstrained parameters in one path segment can cause excessive regular-expression backtracking in DotvvmRoute.IsMatch when a remote requester supplies a long near-match path. DotvvmRouteParser.RouteRegex previously had no matching timeout. Patched runtimes retry with the .NET non-backtracking engine, while runtimes that do not support non-backtracking matching return HTTP 503 after the one-second timeout in DotvvmRoutingMiddleware. This issue is fixed in versions 4.2.11, 4.3.15, and 5.0.0-preview09-final.