How severe is GHSA-6q65-j4jw-9cg8?

GHSA-6q65-j4jw-9cg8 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-6q65-j4jw-9cg8?

GHSA-6q65-j4jw-9cg8 affects the following packages: DotVVM (NuGet), DotVVM (NuGet), DotVVM (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-6q65-j4jw-9cg8?

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.

How do I detect GHSA-6q65-j4jw-9cg8 in my NuGet dependencies?

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.

How do I mitigate GHSA-6q65-j4jw-9cg8 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-6q65-j4jw-9cg8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6q65-j4jw-9cg8 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-6q65-j4jw-9cg8 published, and has it been updated?

GHSA-6q65-j4jw-9cg8 was published on June 19, 2025 and was last updated on June 19, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET

.NET NuGet

Not in CISA KEV

HIGH severity

DotVVM allows path traversal when deployed in Debug modeGHSA-6q65-j4jw-9cg8

HIGHFix: riganti/dotvvm@68db011

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.

Published

Jun 19, 2025

Updated

Jun 19, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Jun 19, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected

.NETDotVVM.NETDotVVM.NETDotVVM

Real-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

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

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`DotVVM`	≥ 4.3.0-preview01-final&&< 4.3.8	4.3.8`dotnet add package DotVVM --version 4.3.8`
.NETNuGet	`DotVVM`	≥ 5.0.0-preview01-final&&< 5.0.0-preview03-final	5.0.0-preview03-final`dotnet add package DotVVM --version 5.0.0-preview03-final`
.NETNuGet	`DotVVM`	all versions	4.2.10`dotnet add package DotVVM --version 4.2.10`

Detection & mitigation playbook

Open-source dependency

Detect
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
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

### 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 De

O3 Security · Impact-Aware SCA

Is GHSA-6q65-j4jw-9cg8 in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works