CVE-2026-41211
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVite+ is a unified toolchain and entry point for web development. Prior to version 0.1.17, `downloadPackageManager()` accepts an untrusted `version` string and uses it directly in filesystem paths. A caller can supply `../` segments or an absolute path to escape the `VP_HOME/package_manager/<pm>/` cache root and make Vite+ delete, replace, and populate directories outside the intended cache location. Version 0.1.17 contains a patch.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceVite+ versions prior to 0.1.17 contain a path traversal vulnerability in the downloadPackageManager() function. An attacker can supply a crafted version string containing '../' path traversal sequences or absolute paths to escape the intended VP_HOME/package_manager/<pm>/ cache directory, allowing arbitrary file deletion, replacement, and directory creation outside the sandbox.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.1.17CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate Vite+ installation and versionRun 'npm list vite-plus' or check package.json for the vite-plus dependency versionAffected if Version is present and less than 0.1.17
-
Identify VP_HOME directoryCheck environment variables or project configuration for VP_HOME path, typically used for Vite+ cachingAffected if VP_HOME is set and the vite-plus version is below 0.1.17
-
Inspect package manager cache directoryExamine VP_HOME/package_manager/<pm>/ directory structure for unexpected files or directories outside the expected cache pathAffected if Files or directories exist outside the intended cache sandbox
-
Check for anomalous file creation or modificationReview file system in VP_HOME parent directory for files created around the time of downloadPackageManager() usageAffected if Unexpected files appear in parent directories of the intended cache location
-
Audit code using downloadPackageManager()Search project source code for calls to downloadPackageManager() and inspect version parameter handlingAffected if User-controlled input is passed directly to the version parameter without validation
You are affected if Vite+ version is below 0.1.17 and the downloadPackageManager() function is invoked with unvalidated input.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.1.17
Upgrade to Vite+ version 0.1.17 or later which contains the patch. If immediate upgrade is not feasible, restrict or validate any user-controlled input passed to the version parameter of downloadPackageManager().
0.1.17
- Check the current installed version of vite-plus (or vite-plus package) in your project by running: npm list vite-plus
- Upgrade to version 0.1.17 or later by running: npm install [email protected] (or npm update vite-plus)
- Verify the upgrade was successful by running: npm list vite-plus
- If you maintain a package-lock.json, ensure it is updated to reflect the new version
- Test that the application functions correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41211 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41211 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data