Loading vulnerability…
CVE-2026-20643 is a WebKit cross-origin vulnerability in the Navigation API caused by insufficient input validation. When WebKit processes maliciously crafted web content, the flaw can allow cross-origin behavior that bypasses the browser Same Origin Policy. Apple states the issue was addressed through improved input validation. The vulnerability affects Apple platforms including iOS, iPadOS, macOS, Safari, and visionOS, and was also disclosed for WebKitGTK and WPE WebKit before version 2.52.1.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
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.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
73 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A WebKit Same Origin Policy bypass vulnerability that could let malicious websites access information belonging to other websites.
A WebKit browser-engine vulnerability involved in malicious web content handling as part of a set of browser security flaws.
A cross-origin issue in the Navigation API that may allow malicious web content to bypass Same Origin Policy.
A WebKit vulnerability caused by improper CORS handling and insufficient input validation in the Navigation API, allowing a remote unauthenticated attacker to bypass the Same Origin Policy using crafted web content.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.