# CVE-2026-96454: Pake grants unrestricted IPC access to every HTTPS origin loaded in generated applications

> Pake grants unrestricted IPC access to all HTTPS origins, allowing malicious web scripts to invoke native commands and achieve code execution.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-jwcr-mx7v-qwwq

## What is CVE-2026-96454?

CVE-2026-96454 is a high-severity missing authorization vulnerability in tw93 Pake, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-923 (Improper Restriction of Communication Channel to Intended Endpoints), CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-96454?


## How do I fix CVE-2026-96454?

No fix has been published for CVE-2026-96454 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-96454 being exploited?

There is no known exploitation of CVE-2026-96454 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-96454 and fix it if it is affected.

What it is: CVE-2026-96454 is a high-severity missing authorization vulnerability in tw93 Pake, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-96454 in the wild and no public exploit code.

Affected product: tw93 Pake. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-96454/ (Markdown: https://insights.sbomify.com/CVE-2026-96454/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-96454
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-96454
- OSV: https://osv.dev/vulnerability/CVE-2026-96454

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-96454/
Summaries are generated and may contain mistakes; the official description above is the record.