VulnerabilityPublished 3 May 2024Updated 2 Aug 2024

CVE-2024-34446: mullvadvpn-app · Improper Restriction of Communication Channel to Intended Endpoints

Affects mullvadvpn-appSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubmullvad/mullvadvpn-app`pkg:github/mullvad/mullvadvpn-app`Other threats	Affected <=2024.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-34446, users and organizations should: 1) Monitor Mullvad VPN updates closely and apply patches immediately once available to ensure proper DNS blocking after tunnel failures. 2) Temporarily disable Mullvad VPN on Android devices if sensitive DNS leakage is unacceptable until a fix is released. 3) Use additional DNS leak protection tools or configure device-level firewall rules to block DNS traffic outside the VPN tunnel. 4) Employ DNS over HTTPS (DoH) or DNS over TLS (DoT) where possible to encrypt DNS queries, reducing exposure even if leakage occurs. 5) Conduct regular network traffic analysis to detect unexpected DNS requests leaving the device. 6) Consider alternative VPN clients with verified DNS leak protections for critical use cases. 7) Educate users about the risk of DNS leaks and encourage cautious use of VPNs during connection failures. These measures go beyond generic advice by focusing on immediate containment of DNS leakage and proactive monitoring until official patches are deployed.

Description

Mullvad VPN through 2024.1 on Android does not set a DNS server in the blocking state (after a hard failure to create a tunnel), and thus DNS traffic can leave the device. Data showing that the affected device was the origin of sensitive DNS requests may be observed and logged by operators of unintended DNS servers.

Impact

The primary impact of CVE-2024-34446 is the compromise of user privacy and confidentiality. Sensitive DNS queries, which can reveal visited domains, user interests, or device location, may be exposed to external DNS servers or network adversaries. This undermines the fundamental privacy guarantees of using a VPN, especially for users relying on Mullvad VPN for anonymity or secure communications. Organizations using Mullvad VPN on Android for secure remote access or privacy protection may face data leakage risks that could lead to targeted surveillance, profiling, or exposure of sensitive operational details. Although the vulnerability does not affect data integrity or availability, the confidentiality breach can have severe consequences in high-risk environments such as journalism, activism, or corporate espionage. The ease of exploitation—requiring no privileges or user interaction—means that any network observer can potentially capture leaked DNS traffic. This broadens the scope of affected systems to all Android devices running the vulnerable Mullvad VPN versions, increasing the global risk footprint.

CWE-923Improper Restriction of Communication Channel to Intended Endpoints (opens in a new tab)
Class weakness
The product establishes a communication channel to (or from) an endpoint for privileged or protected operations, but it does not properly ensure that it is communicating with the correct endpoint.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
OWASP ASVS 4.0.3
V1.14.1 (opens in a new tab)
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
Attack patterns
Contradictory Destinations in Traffic Routing Schemes (opens in a new tab)
Android Activity Hijack (opens in a new tab)
DHCP Spoofing (opens in a new tab)
Infrastructure Manipulation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Mar 2026, 23:17 UTC

WeaknessesCWE-923

Technical details

References

Community reviews

Related threats