The latest version of the Mullvad app resolves DNS leak vulnerabilities affecting users who have “Local network sharing” enabled on either Windows, macOS, or Linux. We strongly recommend all users to upgrade.
Risk of DNS leaks during “transition” states
Since the previous release a few days ago, we have found and fixed a DNS leak vulnerability affecting Windows, macOS, and Linux users (separate from the Window-specific DNS leak below). This bug requires “Local network sharing” to be enabled in the app and for the default DNS resolver to be located on the local private network.
If the above conditions are met, then DNS leaks can occur while the app is in one of the following “transition” states: while trying to connect, while blocked because of an error, or while disconnected with the “Block when disconnected” setting enabled. In other words, not while you are connected.
Windows DNS leak resolved
This release also fixes a vulnerability found specifically in the Windows app version 2020.1. As we had alerted here on the blog, if Windows users had “Local network sharing” enabled in that version, it could enable DNS leaks.
What (else) is new in this version
You’ll probably notice these changes at some point, but we’ll point them out to you anyway:
- Perhaps most noticeable is the new reconnect button on the connection screen (look for the ⟳ symbol). Click this and the app will reestablish your connection.
- On the connection screen, the map view gives a more zoomed-out view of your connection location. We’ve also removed the city and country labels from the map.
- When your account is almost out of time, a system notification will remind you.
- If you’re using an old app version and try to report a problem, a notification will ask you to first upgrade to the latest version and see if the problem still exists.
- (Windows, Linux) The tray icon is larger, and the option to make it monochromatic is now available under the Preferences menu.
Other changes and fixes
- When changing a setting, the app will no longer refresh its connection unless the change is relevant to the connection setup.
- With WireGuard®, the app sometimes got stuck in “creating a secure connection” even though it had successfully connected. This is now fixed.
- (Windows) We fixed "exhausted namespace" installation error that some users on non-English systems experienced with app version 2020.1.
Download the app
Know of someone unable to access our website? Point them to Mullvad's onion address on Tor or Mullvad's GitHub page.
"WireGuard" is a registered trademark of Jason A. Donenfeld.