Description
Pake turns a website into a desktop application built on Tauri. Every application it generates inherits two settings from the upstream template, and together they hand native functionality to untrusted web content.



The first is in src-tauri/capabilities/default.json, which grants IPC access with "remote": { "urls": ["https://*.*"] }. That wildcard tells Tauri to accept IPC from any HTTPS origin, not just the site the application was built to wrap. The second is "withGlobalTauri": true in src-tauri/tauri.conf.json, which puts window.__TAURI__.core.invoke() in reach of ordinary page JavaScript.



Tauri's access control list only checks plugin commands, the ones prefixed with plugin:. Commands the application registers itself through generate_handler!, known as app commands, are never checked against the ACL. So once an origin holds IPC access, it can call every app command with nothing else standing in the way. Pake registers download_file as an app command, and it does not appear in the permissions list because it does not need to.



The practical effect is that any script running on any HTTPS page inside a Pake application can invoke the application's native commands. That includes third-party script the wrapped site loads on its own, such as analytics, advertising, or a compromised CDN. Anyone distributing their own Pake application gets the same access without asking for it. Chained with the path traversal in download_file that is tracked separately as CVE-2026-82635, this reaches arbitrary file write and persistent code execution.
Published: 2026-09-23
Score: 8.2 High
EPSS: < 1% Very Low
KEV: No
Impact: Remote Code Execution via unrestricted IPC and unprotected app commands
Action: Patch
AI Analysis

Impact

Pake turns websites into desktop applications using the Tauri framework. Two default configuration settings give any HTTPS origin loaded in the app permission to use IPC and to invoke native app commands. Because the IPC whitelist is set to "https://*.*" and the withGlobalTauri flag exposes core IPC to page scripts, an attacker can call an app command such as download_file without any access control. That command performs a path traversal, allowing the attacker to write files to arbitrary locations on the host filesystem and thereby achieve persistent code execution.

Affected Systems

The vulnerability affects the Pake desktop application framework developed by tw93. All Pake builds that use the default template – which includes the IPC wildcard "https://*.*" in src-tauri/capabilities/default.json and the withGlobalTauri flag in src-tauri/tauri.conf.json – are impacted. The latest release V3.17.0 (and earlier releases lacking the fix) also fall in the affected range.

Risk and Exploitability

The CVSS score of 8.2 indicates a high severity level. The EPSS score of less than 1% suggests a low likelihood of exploitation currently, and the vulnerability is not listed in the CISA KEV catalog. Exploitation requires a user to run a Pake‑generated application that loads a web page containing malicious or third‑party scripts. The IPC and app command exposure allow the attacker to invoke download_file, enabling path traversal and persistent code execution on the host machine.

Generated by OpenCVE AI on September 23, 2026 at 15:56 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to a Pake release that removes the "https://*.*" entry from src-tauri/capabilities/default.json or that enforces ACL checks on app commands
  • Disable the withGlobalTauri flag in src-tauri/tauri.conf.json unless the application explicitly requires global Tauri access
  • Restrict IPC usage by defining a whitelist that includes only the intended host origin for the wrapped website
  • Audit and remove any third‑party scripts that run in the application’s webview, and enforce a strict Content Security Policy to block elevated origins

Generated by OpenCVE AI on September 23, 2026 at 15:56 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 23 Sep 2026 15:45:00 +0000

Type Values Removed Values Added
First Time appeared Tw93
Tw93 pake
Vendors & Products Tw93
Tw93 pake

Wed, 23 Sep 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Wed, 23 Sep 2026 11:45:00 +0000

Type Values Removed Values Added
Description Pake turns a website into a desktop application built on Tauri. Every application it generates inherits two settings from the upstream template, and together they hand native functionality to untrusted web content. The first is in src-tauri/capabilities/default.json, which grants IPC access with "remote": { "urls": ["https://*.*"] }. That wildcard tells Tauri to accept IPC from any HTTPS origin, not just the site the application was built to wrap. The second is "withGlobalTauri": true in src-tauri/tauri.conf.json, which puts window.__TAURI__.core.invoke() in reach of ordinary page JavaScript. Tauri's access control list only checks plugin commands, the ones prefixed with plugin:. Commands the application registers itself through generate_handler!, known as app commands, are never checked against the ACL. So once an origin holds IPC access, it can call every app command with nothing else standing in the way. Pake registers download_file as an app command, and it does not appear in the permissions list because it does not need to. The practical effect is that any script running on any HTTPS page inside a Pake application can invoke the application's native commands. That includes third-party script the wrapped site loads on its own, such as analytics, advertising, or a compromised CDN. Anyone distributing their own Pake application gets the same access without asking for it. Chained with the path traversal in download_file that is tracked separately as CVE-2026-82635, this reaches arbitrary file write and persistent code execution.
Title Pake grants unrestricted IPC access to every HTTPS origin loaded in generated applications
Weaknesses CWE-862
CWE-923
References
Metrics cvssV3_1

{'score': 8.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:N'}

Subscriptions

Tw93 Pake
cve-icon MITRE

Status: PUBLISHED

Assigner: JFROG

Published:

Updated: 2026-09-23T14:01:32.711Z

Reserved: 2026-09-23T09:53:06.527Z

Link: CVE-2026-96454

cve-icon Vulnrichment

Updated: 2026-09-23T14:01:30.385Z

cve-icon NVD

Status : Received

Published: 2026-09-23T10:17:09.070

Modified: 2026-09-23T15:17:32.557

Link: CVE-2026-96454

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-23T16:00:08Z

Weaknesses
  • CWE-862

    Missing Authorization

  • CWE-923

    Improper Restriction of Communication Channel to Intended Endpoints