Summary
Pake-generated desktop applications expose Tauri IPC to arbitrary HTTPS origins while making the global Tauri API available to page JavaScript. As a result, scripts from wrapped sites, third-party resources, or other HTTPS content may invoke application-registered native commands without authorization; when combined with the separately tracked path traversal issue, this could enable arbitrary file writes and persistent code execution.
Affected context
The issue occurs in Pake applications generated from templates that enable global Tauri access and allow IPC from wildcard HTTPS origins. It is most relevant when an application displays content from external or user-influenced sources, loads third-party scripts, or registers native app commands without applying an authorization check. The exposed download_file command increases the impact when combined with the separately tracked path traversal vulnerability.
Exploit preconditions
- Attack surface: JavaScript running inside a Pake-generated Tauri application
- Required access: The attacker must control, influence, or supply content that is rendered by the application's webview, or rely on a compromised third-party resource loaded by that content
- Trigger point: Invocation of the globally exposed Tauri IPC API from page JavaScript
- Why exploitation is possible: Wildcard HTTPS origin access grants IPC reachability broadly, while application-registered commands are not protected by the plugin-command ACL checks
- Additional condition for file impact: Exploitation of the
download_filepath traversal issue tracked separately as CVE-2026-82635
Why this happens
The underlying bug is a missing authorization boundary between untrusted web content and privileged native application commands. The template combines broad remote-origin IPC permissions with withGlobalTauri, exposing the invocation API to ordinary page scripts. Tauri's ACL enforcement covers plugin commands but does not authorize commands registered directly by the application, allowing reachable app commands to be invoked without command-specific or origin-specific checks. This behavior maps primarily to CWE-862: Missing Authorization and is also related to CWE-923: Improper Restriction of Communication Channel to Intended Endpoints.
Potential impact
- Untrusted page scripts may invoke privileged native application commands
- Attackers could abuse exposed commands to access or manipulate local resources, depending on command behavior
- The
download_filecommand could contribute to arbitrary file writes when chained with CVE-2026-82635 - Arbitrary file writes could enable persistence or code execution in affected deployment contexts
- A compromised third-party script, CDN resource, or wrapped website could gain unintended desktop privileges
General mitigation guidance
Mitigation generally focuses on reducing the trust granted to web content and enforcing authorization at every native command boundary.
Common defensive patterns include:
- Restricting IPC origins to the specific trusted application origin rather than wildcard HTTPS patterns
- Avoiding global exposure of native invocation APIs when page scripts do not require it
- Applying explicit authorization checks to application-registered commands, not only plugin commands
- Allowing native commands to accept only narrowly validated inputs and intended resource locations
- Separating untrusted or third-party content from privileged application contexts
- Running the desktop application with the least local privilege needed for its function
- Treating downloaded content and embedded scripts as untrusted dependencies
How teams detect issues like this
Detection can include:
- Static analysis for broad remote-origin IPC permissions and global Tauri API exposure
- Searches for
generate_handler!registrations that lack command-level authorization checks - Code review of native commands reachable from webview JavaScript, especially file and process operations
- Tests that load content from an untrusted origin and verify that native commands are unavailable or denied
- Policy checks requiring explicit origin allowlists and prohibiting wildcard IPC permissions
- Dependency and supply-chain monitoring for third-party scripts loaded by wrapped sites
Automated code review and configuration-scanning tools can help identify these patterns before applications are distributed.
