Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.4amended

Path traversal in vite-plus/binding downloadPackageManager() writes outside VP_HOME

CVE-2026-41211GHSA-33r3-4whc-44c2

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (vite-plus 0.1.17), 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.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.4 · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H · score source
EPSS
  • CVE-2026-41211: 0.31% estimated exploitation activity in the next 30 days; percentile 24.07 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary downloadPackageManager() in vite-plus/binding accepts an untrusted version string and uses it directly in filesystem paths. A caller can supply ../ segments to escape the VPHOME/packagemanager/<pm/ cache root and cause Vite+ to delete, replace, and populate directories outside the intended cache location. Details The public vite-plus/binding export downloadPackageManager() forwards options.version directly into the Rust package-manager download flow without validating that it is a normal semver version. That value is used as a path component when building the install location under VPHOME. After the package is downloaded and extracted, Vite+: 1. computes the final target directory from the raw version string, 2. removes any pre-existing directory at that target, 3. renames the extracted package into that location, and 4. writes executable shim files there. Because the CLI validates versions via semver::Version::parse() before calling this code, the protection that exists for…

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

    Amended from ghsa record GHSA-33r3-4whc-44c2

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-33r3-4whc-44c2

Agent brief

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

# Patch Next advisory brief: CVE-2026-41211

Advisory: Path traversal in vite-plus/binding downloadPackageManager() writes outside VP_HOME
IDs: CVE-2026-41211, GHSA-33r3-4whc-44c2
Record: https://patchnext.com/advisories/cve-2026-41211 (revision 3, source checked 26 Oct 2026, 12:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: vite-plus 0.1.17. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm vite-plus: affected <= 0.1.16; fixed in 0.1.17

## Suggested inspection (read-only)
- `npm ls vite-plus --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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 vite-plus.
- 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://osv.dev/vulnerability/GHSA-33r3-4whc-44c2 (OSV record GHSA-33r3-4whc-44c2 lists affected ranges: npm vite-plus >=0 <0.1.17 (fixed))
- Verified: https://github.com/advisories/GHSA-33r3-4whc-44c2 (GitHub-reviewed advisory GHSA-33r3-4whc-44c2 lists affected ranges: npm vite-plus >=0 <=0.1.16)

Commands are suggestions: review each one before running it.

Loading voting…