GHSA-6q65-j4jw-9cg8 is a high-severity (CVSS 7.5) vulnerability in DotVVM. A fix is available for DotVVM — see the affected versions and patch details below.
DotVVM allows path traversal when deployed in Debug mode
Real-World Exposure
DotVVM.NETDotVVM.NETDotVVMReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
Description
There is a path traversal vulnerability in any DotVVM application started in Debug mode, if at least one resource with the FileResourceLocation has been added. The vulnerability allows an attacker to read arbitrary files from the filesystem accessible by the web application (i.e. appsettings.json or other files containing secrets).
Patches
The bug is patched in versions 4.2.10, 4.3.8 and 5.0.0-preview03-final (and newer).
Apart from updating DotVVM, it is also recommend invalidating any secrets which could have been leaked by an application deployed in Debug mode (such as database passwords).
Workarounds
If you cannot update to a patched version, avoid running a publicly accessible DotVVM application in Debug mode (Development environment in Asp.Net Core). It is recommend adding the following statement to the DotvvmStartup class:
config.Debug = false; // TODO: workaround for GHSA-6q65-j4jw-9cg8, remove after updating DotVVM
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | DotVVM | ≥ 4.3.0-preview01-final&&< 4.3.8 | 4.3.8dotnet add package DotVVM --version 4.3.8 |
| .NETNuGet | DotVVM | ≥ 5.0.0-preview01-final&&< 5.0.0-preview03-final | 5.0.0-preview03-finaldotnet add package DotVVM --version 5.0.0-preview03-final |
| .NETNuGet | DotVVM | all versions | 4.2.10dotnet add package DotVVM --version 4.2.10 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for DotVVM, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update DotVVM to 4.3.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6q65-j4jw-9cg8 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6q65-j4jw-9cg8 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-6q65-j4jw-9cg8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-6q65-j4jw-9cg8 in your dependencies?
O3 Security finds GHSA-6q65-j4jw-9cg8 across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.