iFrames Bypass Origin Checks for Tauri API Access Control

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.9 · CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:L

EPSS

• CVE-2024-35222: 0.35% estimated exploitation activity in the next 30 days; percentile 28.62 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Remote origin iFrames in Tauri applications can access the Tauri IPC endpoints without being explicitly allowed in the dangerousRemoteDomainIpcAccess in v1 and in the capabilities in v2. This bypasses the origin check and allows iFrames to access the IPC endpoints exposed to the parent window. For this to be exploitable, an attacker must have script execution (e.g. XSS) in a script-enabled iFrame of a Tauri application. Patches The patches include changes to wry and the behaviour of Tauri applications using iFrames. Previously, we injected the Tauri IPC initialization script into iFrames on MacOS, which was unintended. This is now also disabled to be consistent with all other supported operating systems. This means that the Tauri invoke functionality is no longer accessible from iFrames, except on Windows when the origin of the Tauri window and the origin of the iFrame are the same. We have also added a new protection mechanism to the IPC layer to protect against iFrames…

Published by the source

23 May 2024, 14:11 UTC

Last modified by the source

23 May 2024, 16:06 UTC

Source last checked

26 Oct 2026, 15:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-57fm-592m-34r7

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-35222

Advisory: iFrames Bypass Origin Checks for Tauri API Access Control
IDs: CVE-2024-35222, GHSA-57fm-592m-34r7
Record: https://patchnext.com/advisories/cve-2024-35222 (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: tauri 2.0.0-beta.20, 1.6.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io tauri: affected < 1.6.7; >= 2.0.0-beta.0, < 2.0.0-beta.20; fixed in 2.0.0-beta.20, 1.6.7

## Suggested inspection (read-only)
- crates.io tauri: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on tauri.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-57fm-592m-34r7 (GitHub-reviewed advisory GHSA-57fm-592m-34r7 lists affected ranges: crates.io tauri >=0 =2.0.0-beta.0 <2.0.0-beta.20)

Commands are suggestions: review each one before running it.