Apple quietly fixed the iCloud Private Relay IP leak in iOS 26.6.1/macOS 26.6.2. It wasn't patched in the iOS 26.6.1 beta we tested, only the public build. Apple's security release notes make no mention of this fix. https://t.co/W5Q2EEOn30 pic.twitter.com/kP0Tg8Uk6e
— Mysk 🇨🇦🇩🇪 (@mysk_co) August 25, 2026
Update 26/08/26 – 03:20 pm (IST): Apple has now silently fixed this issue, but there’s a catch. It has only been fixed for Safari, and not the other browsers. It was fixed in iOS 26.6.1 and macOS 26.6.2; the release notes don’t mention it. The beta version of it didn’t carry the fix, and it was directly rolled out to the public through the stable version.
Update 06/08/26 – 07:56 pm (IST): Initially, the Mysk account posted that they were in a dilemma about directly reporting the issues to Apple, since their experience with reports hasn’t been very good, riddled with endless delays, inconsistent communication, and more. They’ve shared the reports privately to the Tor Project and also the Orion browser developers, and they’ve disabled WebAuthn and WebTransport by default.
However, they’ve still made Apple aware of the issues. The Psylo account posted that after publishing the blog, they’ve sent its link (and the demo website) to Apple in a security report. The report is already in the “Planning to address…” status, and a fix is planned for the fall of 2026.
Soon after we published the blog, we sent a link to the blog and demo website to Apple in a security report to make them aware of it. Now the report is already in the status "We’re planning to address the issue you reported." and a fix is planned for Fall 2026 🤯🤯🤯 https://t.co/iGWot4mro2 pic.twitter.com/X59t46OEtx
— Psylo: Privacy Browser & Proxy (@psylo_app) August 5, 2026
Original article published on August 05, 2026, follows:
Recently, two iOS developers who run the privacy research project “Mysk” and the private browser Psylo have reported that certain features in Apple’s WebKit engine can disclose a user’s real IP address even when privacy tools are turned on.
The findings were published on the @mysk_co account on X, and a further elaboration is available on the @psylo_app account.
iCloud Private Relay can leak your IP due to issues with WebKit. This affects all iOS browsers that rely on proxy connections, including Psylo (Apple requires all iOS browsers to use WebKit). We just released Version 1.3.1 to address these issues. More details below👇: https://t.co/5kFu0jusih
— Mysk 🇨🇦🇩🇪 (@mysk_co) August 4, 2026
They’ve also released a public test page which you can find here. You can visit the link on your iPhone, and it’ll show you the possible IP leaks, as I’ve demonstrated below.

The problem involves three WebKit behaviors. The first one is “DNS prefetching.” On recent iOS versions, it can skip the proxy and use the device’s normal DNS path instead.
The second loophole involves passkeys. When a site supports passkeys, the system can make a background request that goes straight from the device, which reveals the real IP address. This can happen by just opening the website, without the user needing to sign in. Facebook was given as an example for this.
Finally, there’s WebTransport, which is a newer connection method that can ignore the proxy and expose the real IP address.
These issues affect Safari (based on the WebKit engine) when iCloud Private Relay is enabled. It affects all browsers that use WebKit (which is all browsers on iOS) and route traffic through a proxy, including Psylo, Onion browser, Orion, and more. Since Apple mandates WebKit on all iOS browsers, it’s a problem.
So if you’re a regular user and wondering whether it can happen during normal, everyday browsing, here’s the answer: Yes. According to the researchers, you don’t have to do anything special. Simply opening a website that supports passkeys is enough to trigger an IP leak in some cases.
The other issues (DNS, WebTransport) only occur if the particular site you visit uses these features, but not every site does.
It’s worth noting that system-wide VPNs that tunnel device traffic aren’t affected by this.
The researchers noted that the investigation began after a Psylo user noticed unexpected DNS leaks. Later, these three mechanisms were identified. They’ve also contacted the Tor project and the developers of Onion.
At the time of writing, it’s unclear whether they’ve reported the issues to Apple, and it also matches their earlier decision to stop submitting bugs through Apple’s bounty program.
Psylo has already addressed the problem in v1.3.1 by blocking DNS prefetching and turning off passkeys as well as WebTransport by default. If users still want to continue using these features, they have the option to turn them back on for individual tabs.
In fact, the previous v1.3 update added stronger anti-fingerprinting protection and also improved performance. More on that here.
Featured image: AI