CVE-2024-55884: mullvadvpn-app · n/a
Affects mullvadvpn-appSource CVE Database V5
Not known to be exploited · CVSS 9.0 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 1.3% chance of exploitation in 30 days – higher than 70% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AC:H/AV:N/A:H/C:H/I:H/PR:N/S:C/UI:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Dec 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubmullvad/mullvadvpn-apppkg:github/mullvad/mullvadvpn-appOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Organizations and users should monitor Mullvad’s official channels for patches and apply updates promptly once available. Until patches are released, consider temporarily disabling the affected versions and using alternative VPN solutions with verified security. Implement network-level monitoring to detect unusual exception handling or memory corruption behaviors in VPN clients. Employ endpoint protection solutions capable of detecting heap corruption or anomalous process behavior. Conduct internal audits to identify systems running vulnerable Mullvad versions and prioritize their remediation. Educate users about the risk and advise against using untrusted networks or exposing VPN clients to untrusted code or inputs that might trigger the vulnerability. Collaborate with Mullvad support for guidance and possible workarounds. Finally, maintain robust incident response plans to quickly address potential exploitation attempts.
Description
In the Mullvad VPN client 2024.6 (Desktop), 2024.8 (iOS), and 2024.8-beta1 (Android), the exception-handling alternate stack can be exhausted, leading to heap-based out-of-bounds writes in enable() in exception_logging/unix.rs, aka MLLVD-CR-24-01. NOTE: achieving code execution is considered non-trivial.