Cybersecurity 5 min agoAdd to bookmarks

Researchers at mysk.blog discovered that WebKit—the mandatory engine for all iOS browsers—sends DNS requests and reveals the real IP address before the proxy tunnel is established. iCloud Private Relay does not protect against this behavior.
Researchers at mysk.blog have documented a leak in WebKit (the rendering engine Apple mandates for all browsers on iOS/iPadOS via App Store rules): in certain network configurations, WebKit issues DNS requests or establishes TCP connections before the configured proxy is active, thereby exposing:
This behavior bypasses iCloud Private Relay (Apple’s network privacy feature for iCloud+ subscribers) as well as manually configured VPNs and proxies.
Who is affected:
WKWebView (WebKit’s standard webview component in iOS apps)What may be exposed:
The leak is partial and conditional—it does not apply to all requests but to specific resource-loading behaviors. Still, it is sufficient to compromise network privacy in sensitive contexts.
On Android, Chrome uses Blink, Firefox uses Gecko. On iOS, every browser—Chrome, Firefox, Brave, Opera, DuckDuckGo—is forced to use WebKit by App Store rules. A flaw in WebKit therefore affects 100% of iOS browsers simultaneously, regardless of the vendor.
Apple introduced a partial exception for alternative browsers in the European Union (DMA, 2024), but most iOS users worldwide remain on WebKit.
Users:
Developers:
WKWebView setups with an active proxy and a network capture tool (Charles Proxy, mitmproxy) to detect any out-of-tunnel requestsIf you use iCloud Private Relay or a VPN on iOS to protect your network privacy: update to the next iOS version as soon as it becomes available. Until then, do not rely on these protections for complete anonymity.
Article produced by artificial intelligence, reviewed under human editorial control.