Skip to content

← Actionable
High, CVSS 7.5

DotVVM allows path traversal when deployed in Debug mode

GHSA-6q65-j4jw-9cg8

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (dotvvm 5.0.0-preview03-final, 4.3.8, 4.2.10), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • NuGet dotvvm

    Affected
    >= 4.3.0-preview01-final, <= 4.3.7>= 5.0.0-preview01-final, < 5.0.0-preview03-final< 4.2.10
    Fixed in
    4.2.10, 5.0.0-preview03-final, 4.3.8

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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:

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-6q65-j4jw-9cg8

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-6q65-j4jw-9cg8

Advisory: DotVVM allows path traversal when deployed in Debug mode
IDs: GHSA-6q65-j4jw-9cg8
Record: https://patchnext.com/advisories/ghsa-6q65-j4jw-9cg8 (revision 1, source checked 26 Oct 2026, 17:03 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: dotvvm 5.0.0-preview03-final, 4.3.8, 4.2.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet dotvvm: affected >= 4.3.0-preview01-final, <= 4.3.7; >= 5.0.0-preview01-final, < 5.0.0-preview03-final; < 4.2.10; fixed in 4.2.10, 5.0.0-preview03-final, 4.3.8

## Suggested inspection (read-only)
- NuGet dotvvm: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on dotvvm.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6q65-j4jw-9cg8 (GitHub-reviewed advisory GHSA-6q65-j4jw-9cg8 lists affected ranges: NuGet dotvvm >=4.3.0-preview01-final =5.0.0-preview01-final =0 <4.2.10)

Commands are suggestions: review each one before running it.

Loading voting…