Tauri is a framework for building binaries for all major desktop platforms. This advisory is not describing a vulnerability in the Tauri code base itself but a commonly used misconfiguration which could lead to leaking of the private key and updater key password into bundled Tauri applications using the Vite frontend in a specific configuration. The Tauri documentation used an insecure example configuration in the `Vite guide` to showcase how to use Tauri together with Vite. Copying the following snippet `envPrefix: ['VITE_', 'TAURI_'],` from this guide into the `vite.config.ts` of a Tauri project leads to bundling the `TAURI_PRIVATE_KEY` and `TAURI_KEY_PASSWORD` into the Vite frontend code and therefore leaking this value to the released Tauri application. Using the `envPrefix: ['VITE_'],` or any other framework than Vite means you are not impacted by this advisory. Users are advised to rotate their updater private key if they are affected by this (requires Tauri CLI >=1.5.5). After updating the envPrefix configuration, generate a new private key with `tauri signer generate`, saving the new private key and updating the updater's `pubkey` value on `tauri.conf.json` with the new public key. To update your existing application, the next application build must be signed with the older private key in order to be accepted by the existing application.
Tauri is a framework for building binaries for all major desktop platforms. This advisory is not describing a vulnerability in the Tauri code base itself but a commonly used misconfiguration which could lead to leaking of the private key and updater key password into bundled Tauri applications using the Vite frontend in a specific configuration. The Tauri documentation used an insecure example configuration in the `Vite guide` to showcase how to use Tauri together with Vite. Copying the following snippet `envPrefix: ['VITE_', 'TAURI_'],` from this guide into the `vite.config.ts` of a Tauri project leads to bundling the `TAURI_PRIVATE_KEY` and `TAURI_KEY_PASSWORD` into the Vite frontend code and therefore leaking this value to the released Tauri application. Using the `envPrefix: ['VITE_'],` or any other framework than Vite means you are not impacted by this advisory. Users are advised to rotate their updater private key if they are affected by this (requires Tauri CLI >=1.5.5). After updating the envPrefix configuration, generate a new private key with `tauri signer generate`, saving the new private key and updating the updater's `pubkey` value on `tauri.conf.json` with the new public key. To update your existing application, the next application build must be signed with the older private key in order to be accepted by the existing application.
Tauri is a framework for building binaries for all major desktop platforms. This advisory is not describing a vulnerability in the Tauri code base itself but a commonly used misconfiguration which could lead to leaking of the private key and updater key password into bundled Tauri applications using the Vite frontend in a specific configuration. The Tauri documentation used an insecure example configuration in the `Vite guide` to showcase how to use Tauri together with Vite. Copying the following snippet `envPrefix: ['VITE_', 'TAURI_'],` from this guide into the `vite.config.ts` of a Tauri project leads to bundling the `TAURI_PRIVATE_KEY` and `TAURI_KEY_PASSWORD` into the Vite frontend code and therefore leaking this value to the released Tauri application. Using the `envPrefix: ['VITE_'],` or any other framework than Vite means you are not impacted by this advisory. Users are advised to rotate their updater private key if they are affected by this (requires Tauri CLI >=1.5.5). After updating the envPrefix configuration, generate a new private key with `tauri signer generate`, saving the new private key and updating the updater's `pubkey` value on `tauri.conf.json` with the new public key. To update your existing application, the next application build must be signed with the older private key in order to be accepted by the existing application.
### Impact
This advisory is not describing a vulnerability in the Tauri code base itself but a commonly used misconfiguration which could lead to leaking of the private key and updater key password into bundled Tauri applications using the Vite frontend in a specific configuration.
The Tauri documentation used an insecure example configuration in the [Vite guide](https://tauri.app/v1/guides/getting-started/setup/vite/) to showcase how to use Tauri together with Vite.
Copying the following snippet `envPrefix: ['VITE_', 'TAURI_'],` from this guide into the `vite.config.ts` of a Tauri project possibly leads to bundling the `TAURI_PRIVATE_KEY` and `TAURI_KEY_PASSWORD` into the Vite frontend code and therefore leaking this value to the debug built of a Tauri application.
The value is automatically bundled into debug builds but for production builds it is not embedded, as long as it is not directly referenced in the frontend code. Vite statically replaces these values in production builds. This reduces the amount of affected applications to a very small amount of affected applications.
To verify if you are affected you can search for the private key value or the `TAURI_PRIVATE_KEY` variable inside the release build frontend assets (`dist/`).
> Example: `grep -r "TAURI_PRIVATE_KEY" dist/`
Using only the `envPrefix: ['VITE_'],` or any other framework than Vite means you are not impacted by this advisory.
### Patches
The documentation has been patched but as the root cause is not in Tauri itself the issue is not fixed by updating Tauri.
The `vite.config.ts` configuration of the project needs to be adapted.
We recommend rotating your updater private key if you are affected by this (requires Tauri CLI >=1.5.5). After updating the envPrefix configuration, generate a new private key with `tauri signer generate`, saving the new private key and updating the updater's `pubkey` value on `tauri.conf.json` with the new public key. To update your existing application, the next application build must be signed with the older private key in order to be accepted by the existing application.
### Workarounds
The `envPrefix: ['VITE_'],`should be used and the desired `TAURI` variables manually added.
Respective these variables could be added `TAURI_PLATFORM`, `TAURI_ARCH`, `TAURI_FAMILY`, `TAURI_PLATFORM_VERSION`, `TAURI_PLATFORM_TYPE` and `TAURI_DEBUG` without leaking sensitive information.
We urge affected users to implement the workaround as the `1.x` branch will not receive a general prevention fix as it would break systems.
### References
The issue was originally disclosed in our discord [here](https://discord.com/channels/616186924390023171/1164260301655523409).
The affected guide is [https://tauri.app/v1/guides/getting-started/setup/vite/](https://tauri.app/v1/guides/getting-started/setup/vite/).
> Update: We lowered the severity from high to low, as the likelihood of impact was found to only affect a **very limited** amount of applications.
> Update2: We changed the affected versions to make clear that after `2.0.0-alpha.16` or `1.5.6` the potentially vulnerable recommendation was no longer visible on our website and should not affect projects by default. A lot of users were confused and we believe this advisory reached the necessary user base.
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Oct 19, 2023, 11:35:03 PM
dateUpdated: Sep 12, 2024, 3:50:32 PM
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Modified
Weakness classifications: CWE-200 · CWE-522
Original publisher date fields
published: 2023-10-20T00:15:16.920
lastModified: 2026-06-17T06:30:10.760
16 source CPE criteria · context only
cpe:2.3:a:tauri:tauri:*:*:*:*:*:*:*:*
cpe:2.3:a:tauri:tauri:2.0.0:alpha0:*:*:*:*:*:*
cpe:2.3:a:tauri:tauri:2.0.0:alpha10:*:*:*:*:*:*
cpe:2.3:a:tauri:tauri:2.0.0:alpha11:*:*:*:*:*:*
cpe:2.3:a:tauri:tauri:2.0.0:alpha12:*:*:*:*:*:*
cpe:2.3:a:tauri:tauri:2.0.0:alpha13:*:*:*:*:*:*
cpe:2.3:a:tauri:tauri:2.0.0:alpha14:*:*:*:*:*:*
cpe:2.3:a:tauri:tauri:2.0.0:alpha15:*:*:*:*:*:*
cpe:2.3:a:tauri:tauri:2.0.0:alpha2:*:*:*:*:*:*
cpe:2.3:a:tauri:tauri:2.0.0:alpha3:*:*:*:*:*:*
cpe:2.3:a:tauri:tauri:2.0.0:alpha4:*:*:*:*:*:*
cpe:2.3:a:tauri:tauri:2.0.0:alpha5:*:*:*:*:*:*
cpe:2.3:a:tauri:tauri:2.0.0:alpha6:*:*:*:*:*:*
cpe:2.3:a:tauri:tauri:2.0.0:alpha7:*:*:*:*:*:*
cpe:2.3:a:tauri:tauri:2.0.0:alpha8:*:*:*:*:*:*
cpe:2.3:a:tauri:tauri:2.0.0:alpha9:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.