Tauri Tauri 2.0.0 Alpha 8
Approved changes feed: RSS · Atom
cpe:2.3:a:tauri:tauri:2.0.0:alpha8:*:*:*:*:*:*part: a version: 2.0.0 update: alpha8
| Vendor | Tauri (5a9210d2-dda5-53dc-a17a-f3dcaebc9655) |
|---|---|
| Product | Tauri (b86aa9dd-2a59-5d2f-84e7-38d6d8307649) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from NVD CPE 2.0 feed
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/tauri-apps/tauri |
purl2cpe | 2026-06-01 10:13:20.719728 |
pkg:sourceforge/tauri.mirror |
purl2cpe | 2026-06-01 10:13:20.719729 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-46115 |
vulnerable | 2026-06-08 06:12:43.868368 |
Updater Private Keys Possibly Leaked via Vite Environment Variables in tauri-cli
HIGH (8.4)
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.
Published: 2023-10-19T23:35:03.875Z
Updated: 2024-09-12T15:50:32.414Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.