Return to Facebook   Twitter   Reddit   Instagram   Mastodon   ProtonMail

VPN bypass vulnerability in Apple iOS

Posted on March 25th, 2020 by in Security.

UPDATE July 24, 2020: We can confirm this bug still exists in iOS version 13.6.

UPDATE June 1, 2020: Apple’s release notes for iOS version 13.5 do not mention this issue, and we have confirmed that the bug still exists in the new version.

This article reports a security vulnerability discovered in Apple’s iOS version 13.4 that prevents VPNs from encrypting all traffic. 

From time to time we may encounter vulnerabilities in third-party software, which in the future will be disclosed after 90 days in accordance with our responsible disclosure program. We are disclosing this “VPN bypass” vulnerability publicly because it’s important that our community and other VPN providers and their users are aware of this issue.

Below we explain the nature of the security flaw, how we investigated it, and what users can do to mitigate their risk until Apple fixes the vulnerability.

How the iOS VPN bypass vulnerability works

Typically, when you connect to a virtual private network (VPN), the operating system of your device closes all existing Internet connections and then re-establishes them through the VPN tunnel. 

Learn more: how VPNs work

A member of the Proton community discovered that in iOS version 13.3.1, the operating system does not close existing connections. (The issue also persists in the latest version, 13.4.) Most connections are short-lived and will eventually be re-established through the VPN tunnel on their own. However, some are long-lasting and can remain open for minutes to hours outside the VPN tunnel. 

One prominent example is Apple’s push notification service, which maintains a long-running connection between the device and Apple’s servers. But the problem could impact any app or service, such as instant messaging applications or web beacons. 

The VPN bypass vulnerability could result in users’ data being exposed if the affected connections are not encrypted themselves (though this would be unusual nowadays). The more common problem is IP leaks. An attacker could see the users’ IP address and the IP address of the servers they’re connecting to. Additionally, the server you connect to would be able to see your true IP address rather than that of the VPN server.

Those at highest risk because of this security flaw are people in countries where surveillance and civil rights abuses are common.

Neither ProtonVPN nor any other VPN service can provide a workaround for this issue because iOS does not permit a VPN app to kill existing network connections.

Investigating the vulnerability

To investigate this issue, we used Wireshark to capture an iOS device’s network traffic. 

When you connect a device to VPN, you should only be able to see traffic between the device’s IP and the VPN server or local IP addresses (other devices on your local network). As the capture below shows, there is also direct traffic between the iOS device’s IP and an external IP address that is not the VPN server (in this case it’s an Apple server).

IOS device’s network traffic on wireshark = iOS device’s IP address = ProtonVPN server = Apple-owned IP address

We’ve calculated this vulnerability’s CVSS score as medium.

How to mitigate the iOS VPN bypass vulnerability

Internet connections established after you connect to VPN are not affected. But connections that are already running when you connect to VPN may continue outside the VPN tunnel indefinitely. There is no way to guarantee that those connections will be closed at the moment you start a VPN connection. 

However, we’ve discovered the following technique to be almost as effective:

  1. Connect to any ProtonVPN server.
  2. Turn on airplane mode. This will kill all Internet connections and temporarily disconnect ProtonVPN. 
  3. Turn off airplane mode. ProtonVPN will reconnect, and your other connections should also reconnect inside the VPN tunnel, though we cannot guarantee this 100%.

Alternatively, Apple recommends using Always-on VPN to mitigate this issue. This method requires using device management, so unfortunately it doesn’t mitigate the issue for third-party applications such as ProtonVPN.

This vulnerability was first reported to us by Luis, a security consultant and member of the Proton community. We have been in contact with Apple, which has acknowledged the VPN bypass vulnerability and is looking into options to mitigate it. Until an update is available from Apple, we recommend the above workarounds.

This article was updated March 26, 2020.

We are the scientists, engineers, and developers who build ProtonMail, the world's largest encrypted email service. We're now building ProtonVPN also to ensure that everybody can have access to free and secure internet.

Post Comment


  1. Matti

    iOS 13.6 was just released and includes the following in its release notes;
    “Provides a mechanism for administrators to specify domains to exclude from traffic carried by always-on VPN connections”

    I’m not sure what they mean by “administrators” but what’s ProtonVPN’s take on this, and will you be leveraging it it future? More importantly, has iOS 13.6 (finally) fixed that VPN bypass bug mentioned here?

  2. Ben Wolford

    Unfortunately, 13.6 does not fix the bypass issue. The item in the release notes you mentioned allows organizations to control and configure employee devices. It’s not accessible to apps like ProtonVPN.

  3. Nora

    iOS 13

  4. Kevin Nelson

    After testing with iOS 14 beta (18A5301v), it appears the issue no longer exists.

  5. Tommy

    Is it fixed in iOS 13.5.1?

  6. Roxana Zega

    Hi Tommy,

    We are not aware of any fix. We will inform users if/when we have news.


  7. w

    13.5.1 Fix it?

  8. Tommy

    Is this fixed in the most recent update 13.5.1?

  9. Tommy

    Is this fixed in 13.5.1?

  10. flo

    how you know that ? @Stefan ( source please )

  11. Stefan

    Apple informed us that it is not fixed with 13.5.
    They are still working on it.

  12. Koko

    Hi, I was wondering if this bug is finally solved with the 13.5 update.

  13. Richie Koch

    Hi Koko, we’re still awaiting official word from Apple. They do not mention in their latest security update, but we are monitoring the situation. We will alert users if/when we have news.

  14. Daniele

    What about the 13.4.1 ?

  15. Roxana Zega

    Hi Daniele,

    Apple hasn’t confirmed the fix and it hasn’t informed us either.


  16. Ben

    I think this was fixed in yesterdays iOS 13.4.1 update

  17. Roxana Zega

    Hi Ben,

    Apple hasn’t confirmed the fix and it hasn’t informed us either.


  18. Michael Alem

    Is the issue affecting lte cellular not to connect with ProtonVPN and if so has it been fixed on the latest iOS 13.4.1

  19. Roxana Zega

    Hi Michael,

    Apple hasn’t confirmed the fix and it hasn’t informed us either.


  20. Johan

    Does 13.4.1 resolve the bug?

  21. Roxana Zega

    Hi Johan,

    Apple hasn’t confirmed the fix and it hasn’t informed us either.


  22. AlexDrPol

    Thanks for your hard work to ensure our privacy.

  23. Advalorem

    Not fun at all.

  24. nitrohorse

    Does this issue only affect IKEv2 VPN configurations (“personal VPNs”) or also OpenVPN and WireGuard VPN configurations?

  25. Richie Koch

    Hello! Unfortunately, this bug affects all VPN protocols.

  26. Orlando Smith

    Is it time for Apple to authorize and securely enable at least trustworthy VPNs, such as ProtonVPN, to execute a kill switch in iOS? I think so, unless it has a good security reason for not doing so; a reason of commercial benefit won’t do.

    Apple may have to do this, because, other than commerical advantage, its seemingly regular appearance of VPN impairing flaws in iOS could be construed as a curiously coincidental benefit to intelligence agencies, which constantly seek to compromise major operating systems so as to conduct clandestine surveillance of individuals.

  27. Tahir Raza

    I am also facing issue in my app where i send an encrypted key, its producing an invalid key hence the app is breaking !

    Apple should look into this asap

  28. David Schwartz

    If you are at home you can turn off your phone network connection and then connect via WIFI to a ProtonVPN connected FlashRouter for VPN protection, instead of using iOS apps. The only external internet available would now be through an active VPN connection from the router.

  29. Orlando Smith

    I’ve also just yelled at Apple about this. Apple is on pace to introduce one significant VPN security flaw with every update to iOS. Smoke can be seen to come from Steve Jobs’ grave as he spins at over 50,000 RPMs.

    I think that the problem is that Apple’s engineers are trying to serve two masters. They are designing iOS to fully exploit the commercial opportunities of iTunes’ streaming, apps, etc., as they try to makes iOS secure and protective of users’ privacy. At critical junctures, those two things will be difficult to reconcile. And since Apple’s engineers will be managed for profits first, security and privacy will be at times compromised, probably inadvertently compromised but compromised nonetheless, and then Apple will fix the security and/or privacy flaw, as best as it can be fixed, after the fact.

    Really makes me consider whether I want to upgrade to Apple’s coming laptops with Apple’s own CPU/GPU that will run a derivative iOS operating system?

  30. CyberneticistB

    Thank you ProtonVPN for continuously working to protect our data and privacy. 🙂

  31. Richie Koch

    You’re very welcome. We simply cannot stand by while so many companies and organizations refuse to respect the fundamental human right to privacy.

  32. Stubbles

    Did you guys get any bounty for this?

  33. John

    Hmm does WireGuard (or even OpenVPN) on iOS have the same issue? Because don’t they have different behavior than IKEv2?

  34. Richie Koch

    This is a good question. However, this bug affects all VPN protocols.

  35. J B

    Is the vulnerability also present in iOS 13.4 that was released yesterday?

  36. Richie Koch

    Yes, the issue also persists in the latest version, 13.4. We have updated the blog post.

Leave a Reply

Your email address will not be published. Required fields are marked *

Knowledge base


Secure your internet

Get ProtonVPN

For customer support inquiries, please submit the following form for the fastest response:

For all other inquiries:

You can also Tweet to us: