George Chandra Eka
A critical vulnerability has been identified within Apple’s iCloud Private Relay service, a feature designed to obscure users’ IP addresses and enhance online privacy. Security researchers Talal Haj Bakry and Tommy Mysk have uncovered that Private Relay does not consistently function as intended, potentially exposing users’ real IP addresses to websites and services due to underlying issues within Apple’s WebKit browser engine. This revelation poses significant questions about the efficacy of Apple’s privacy safeguards and the inherent challenges in building truly anonymizing online experiences.
The Discovery of a Critical Privacy Flaw
The core of the problem, as detailed by Bakry and Mysk, lies in specific scenarios involving passkeys—a burgeoning password-free login method—and the architecture of Apple’s WebKit. While Private Relay is engineered to create a two-hop relay system that separates a user’s IP address from their browsing activity, ensuring neither Apple nor third-party websites can trace their online identity, the researchers’ findings indicate a bypass mechanism. When a user employs a passkey to authenticate on a website or service, the device initiates an authentication request that, under certain circumstances, occurs outside the protective tunnel of Private Relay.
Private Relay, an integral component of the iCloud+ subscription service, is primarily integrated with Safari and designed to shield web traffic originating from the browser. However, unlike a comprehensive Virtual Private Network (VPN) that encrypts and reroutes all device-level internet traffic, Private Relay’s scope is more confined. This distinction becomes critical when considering passkey authentication. Passkeys, built on the FIDO (Fast Identity Online) Alliance standards, leverage cryptographic keys stored securely on a user’s device. When logging in, the device communicates directly with the service provider to verify the passkey. This direct communication, the researchers explain, can circumvent Private Relay’s protection, thereby revealing the user’s actual IP address.
The implications extend beyond Safari. Given that Apple mandates the use of WebKit for all web browsers on its iOS platform, the vulnerability is not isolated to Apple’s native browser. Third-party browsers, even those explicitly designed with enhanced privacy and anonymity in mind, such as OnionBrowser and the researchers’ own Psylo browser, are also susceptible to this IP leak when passkeys are utilized. This highlights a systemic issue within the foundational web engine of the iOS ecosystem, rather than a mere application-specific bug.
Background: Apple’s Stance on Privacy and Private Relay’s Genesis
Apple has, for years, positioned itself as a champion of user privacy, often contrasting its data practices with those of other tech giants. This commitment is a cornerstone of its marketing and product development philosophy. iCloud Private Relay, introduced with iOS 15 and macOS Monterey in the fall of 2021, was a significant manifestation of this commitment. It was heralded as an innovative approach to internet privacy, aiming to offer a layer of protection akin to a VPN but with a more integrated and user-friendly experience for iCloud+ subscribers.
The service operates by routing user traffic through two distinct internet relays. The first relay, operated by Apple, assigns an anonymous IP address that maps to the user’s approximate region but not their precise location. This relay also decrypts the DNS (Domain Name System) request, which typically reveals the website a user intends to visit. The encrypted DNS request is then passed to the second relay. The second relay, operated by a third-party content provider, assigns a temporary, anonymous IP address and forwards the user to their destination website. Crucially, neither Apple nor the second relay operator has full visibility into both the user’s real IP address and their browsing destination, theoretically preventing a single entity from building a comprehensive profile of the user’s online activity.
Despite its privacy-enhancing design, Private Relay has always had certain limitations. It is not a full VPN and does not encrypt all internet traffic from a device; rather, it focuses on Safari browsing and certain insecure HTTP app traffic. Furthermore, its availability has been subject to regional restrictions due to regulatory complexities, particularly in countries like China, Saudi Arabia, and Egypt, where its functionality is either limited or entirely unavailable. These pre-existing limitations underscore the complex landscape of internet privacy and the technical hurdles in implementing robust anonymization services. The current discovery of an IP leak through WebKit and passkeys, however, represents a more fundamental breach of the feature’s core promise.
The Ascendance of Passkeys and Their Unintended Interaction
Passkeys represent a significant stride towards a passwordless future, offering a more secure and convenient alternative to traditional passwords. Developed under the FIDO Alliance, passkeys leverage public-key cryptography, where a unique cryptographic key pair is generated for each online account. One key remains private on the user’s device (e.g., iPhone, Mac), while the public key is stored by the website or service. Authentication occurs when the device proves possession of the private key, typically through biometric verification (Face ID or Touch ID) or a device PIN.
The primary advantages of passkeys are manifold: they are phishing-resistant, as the authentication process is tied to the specific website’s origin; they are immune to server-side data breaches (as no password hashes are stored); and they are designed to be cross-platform and cross-device. Major tech companies, including Apple, Google, and Microsoft, have enthusiastically adopted and promoted passkeys, heralding them as a superior security paradigm.
The irony of the current vulnerability is that a feature designed to enhance security (passkeys) is inadvertently undermining a feature designed to enhance privacy (Private Relay). The very mechanism that makes passkeys robust—their direct, device-level cryptographic communication—appears to bypass the intended privacy protections of Private Relay. This highlights a critical challenge in modern cybersecurity: the intricate interplay between different security and privacy mechanisms, and the potential for unforeseen interactions that create new vulnerabilities. As passkey adoption continues to grow, becoming a default login method for an increasing number of online services, the scope of this IP leak potential will expand proportionately, affecting a larger user base.
Chronology of Discovery and Disclosure
The timeline of the discovery, as outlined by the researchers, sheds light on the process of uncovering such intricate flaws. The initial clue emerged in late June 2026, when a user reported a DNS leak within Psylo, one of the privacy-focused browsers developed by Mysk and Bakry. This report prompted a deeper investigation by the research team. During their exhaustive analysis, they uncovered not only the DNS leak but also the broader issue of IP address exposure through WebKit, specifically in the context of passkey authentication.
Following their comprehensive findings, the researchers adhered to responsible disclosure practices. They promptly contacted OnionBrowser and the Tor Project, the organization behind the anonymity network utilized by OnionBrowser, to share their technical findings and proposed solutions. This proactive communication aimed to empower these privacy-focused entities to address the vulnerability within their own implementations, given their reliance on WebKit.
On August 5, 2026, the researchers publicly disclosed their findings via a detailed post on X (formerly Twitter). Their post not only outlined the technical specifics of the vulnerability but also candidly discussed the ethical dilemma inherent in responsible disclosure, particularly when dealing with fundamental platform-level issues. They emphasized the potential for delays in fixes from large corporations like Apple, referencing previous experiences.
Apple, upon being contacted by 404Media regarding the researchers’ report, confirmed that it is investigating the matter. This official acknowledgment signifies that the company is aware of the vulnerability and is likely mobilizing its engineering teams to assess and, eventually, address the problem. However, the researchers’ cautious outlook on the timeline for a fix is informed by historical precedents. They specifically cited the vulnerability discovered in iCloud’s "Hide My Email" feature in mid-2025, which allowed real email addresses to be leaked despite the use of aliases. Apple took approximately a year to roll out a comprehensive fix for that issue, suggesting that complex, platform-level vulnerabilities often require significant time and resources to resolve effectively across a vast ecosystem of devices and services.
Official Responses and Broader Implications
The immediate response from Apple, confirming an ongoing investigation, is standard procedure for a company of its stature when confronted with security and privacy vulnerabilities. While reassuring to a degree, it offers little in terms of immediate mitigation for users. The lack of a definitive timeline for a fix means users relying on Private Relay for IP anonymity, especially those increasingly adopting passkeys, remain exposed.
The researchers’ proactive outreach to OnionBrowser and the Tor Project is commendable, demonstrating a commitment to securing the broader privacy ecosystem. It is reasonable to infer that these organizations are actively reviewing the findings and considering how to best protect their users, potentially through workarounds or by urging Apple for a swift resolution. For users of these browsers, the news is particularly concerning, as they often choose these platforms precisely for their enhanced privacy guarantees, which are now shown to be compromised by an underlying platform issue.
From a broader perspective, this vulnerability has several significant implications. Firstly, it could erode user trust in Apple’s long-standing privacy narrative. While no system is entirely foolproof, a core feature designed explicitly to mask IP addresses failing under common usage scenarios (like passkey authentication) can diminish confidence in Apple’s privacy architecture. This is particularly salient as Apple often differentiates itself from competitors based on its commitment to user data protection.
Secondly, the issue reinforces concerns about Apple’s "walled garden" approach, specifically the mandate for all iOS browsers to use WebKit. While this ensures a consistent user experience and security baseline, it also means that a vulnerability in WebKit can propagate across the entire browser ecosystem on iOS, leaving no truly independent browser immune. This lack of choice in browser engines can be seen as a double-edged sword: offering uniformity but also centralized points of failure for privacy and security.
Thirdly, the incident underscores the intricate challenges in balancing security and privacy in a rapidly evolving digital landscape. As new authentication methods like passkeys gain traction for their security benefits, their integration with existing privacy features must be meticulously scrutinized to prevent unintended side effects. The complexity of modern software stacks means that seemingly isolated components can have unforeseen interactions that compromise overall system integrity.
Finally, this discovery could invite further scrutiny from privacy advocates and regulatory bodies. Governments and consumer protection agencies worldwide are increasingly focused on holding tech companies accountable for their privacy promises. A demonstrated failure of a prominent privacy feature could lead to calls for greater transparency, faster remediation, and potentially new regulations concerning how privacy features are implemented and advertised.
Recommendations for Users and the Path Forward
While Apple investigates and works on a fix, users who are highly concerned about their IP address being revealed should consider additional layers of protection. A full-fledged, reputable Virtual Private Network (VPN) service that operates at the device level, encrypting all outgoing and incoming traffic, remains the most robust solution for masking IP addresses across all applications, not just browsers. Users should also ensure their iOS devices are updated to the latest available software versions, as Apple typically rolls out security patches and feature fixes through system updates.
For those using passkeys, being aware of this potential vulnerability is crucial. Until a fix is implemented, users may choose to limit their use of passkeys on websites where IP anonymity is paramount, or combine passkey usage with a comprehensive VPN.
Looking ahead, Apple will likely need to implement a multi-faceted solution. This could involve significant updates to WebKit to ensure that all network requests, including those initiated by passkeys, are properly routed through Private Relay. It might also necessitate architectural changes to Private Relay itself, perhaps extending its scope to cover more device-level traffic or refining its integration with core iOS services. The duration of the fix will be a critical factor in how this incident is perceived by the user base and the broader cybersecurity community. The expectation will be for Apple to not only patch the vulnerability but also to provide clear communication about the issue, its resolution, and reaffirm its commitment to user privacy in a transparent manner. The saga of Private Relay’s IP leak serves as a potent reminder that in the intricate world of digital privacy, vigilance and continuous scrutiny remain paramount.
