Skip to main content
Mallory
MediumPublic exploit

Same Origin Policy bypass in WebKit Navigation API

IdentifiersCVE-2026-20643CWE-346· Origin Validation Error

CVE-2026-20643 is a WebKit cross-origin vulnerability in the Navigation API. Apple describes it as a cross-origin issue addressed with improved input validation. When WebKit processes maliciously crafted web content, the flaw can allow bypass of the browser Same Origin Policy (SOP), a core isolation boundary intended to prevent one origin from accessing data belonging to another. The issue affects Apple platforms and browsers/components using the vulnerable WebKit code, including Safari/WebKit on iOS, iPadOS, macOS, visionOS, and WebKitGTK/WPE WebKit before 2.52.1. Publicly available details do not identify the exact vulnerable function, but the bug is specifically tied to Navigation API handling of cross-origin input.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation may allow a malicious website or webpage to break origin isolation and access data or interactions that should be restricted to a different origin. Reported consequences include the ability to bypass Same Origin Policy protections, potentially exposing session tokens, credentials, or other sensitive information from other sites the victim is authenticated to, and enabling follow-on attacks such as session hijacking or data exfiltration from trusted web applications.

Mitigation

If you can’t patch tonight, do this now.

Until patches are fully deployed, reduce exposure by disabling or tightly controlling automatic browsing to untrusted sites, using browser isolation where available, and enforcing rapid patch compliance through MDM or equivalent fleet management. High-risk users should enable Apple Lockdown Mode where supported. Organizations should verify that Apple Background Security Improvements have actually been applied, including checking the relevant sub-version suffixes on managed devices, rather than assuming silent deployment succeeded.

Remediation

Patch, then assume compromise.

Apply the vendor fixes. Apple states the issue was fixed with improved input validation in Background Security Improvements for iOS, iPadOS, and macOS, and in Safari 26.4, iOS 18.7.7, iPadOS 18.7.7, iOS 26.4, iPadOS 26.4, macOS Tahoe 26.4, and visionOS 26.4. For WebKitGTK and WPE WebKit, upgrade to version 2.52.1 or later. Ensure Apple Background Security Improvements / automatic security updates are enabled where applicable so the out-of-band fix is installed.
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).

VALID 1 / 2 TOTALView more in app
CVE-2026-20643MaturityPoCVerified exploit

This repository is a small browser-based proof of concept for CVE-2026-20643 targeting WebKit Navigation API behavior during cross-port navigations. It contains four files: a minimal README referencing the CVE, a standalone demonstration page (index.html), a more formal test case (navigate-event-canintercept-cross-port.html), and a bundled WebKit/WPT-style reporting helper (resources/testharnessreport.js). The core capability is not remote code execution or payload delivery; instead, it exercises a browser security boundary condition. Both HTML files compute the current port, switch to a different port on the same hostname (8000 <-> 8800), build a target URL, register a 'navigate' event listener on the Navigation API, trigger navigation by programmatically clicking an anchor, and inspect event.canIntercept. Correct behavior is that canIntercept must be false for cross-port navigations. The standalone page logs the observed value to the DOM and console, while the test-harness page asserts the expected value and resolves a promise after preventing the navigation. The repository structure suggests a vulnerability reproduction and regression-test setup rather than a weaponized exploit. index.html is the easiest manual entry point for reproducing the issue in a browser. navigate-event-canintercept-cross-port.html is a more formal automated test suitable for browser testing environments. resources/testharnessreport.js is generic support code for WebKit test execution and result formatting; it is not exploit logic itself, though it references test environment ports 8800 and 9443. No hardcoded external domains or IPs are contacted. The only network target is a dynamically generated same-host URL on a different port, making the exploit behavior dependent on how the page is served. Overall, this is a focused PoC/regression test for a browser-side cross-port navigation interception flaw in WebKit.

FlivDisclosed Mar 20, 2026markdownhtmlbrowsernetwork
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AppleIosoperating_system
AppleIpadosoperating_system
AppleIphone Osoperating_system
AppleMacosoperating_system
Rocky LinuxRocky Linuxoperating_system
WebkitgtkWebkit2gtk3application

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware1

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity55

Community discussion across Reddit, Mastodon, and other social sources.