# CVE-2026-19380: Mullvad wireguard.sys IOCTL AdapterState reference count

> A local attacker can exploit a reference count error in the Mullvad WireGuard kernel driver to achieve privilege escalation or code execution.

- **Severity:** Medium 4.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-vfrx-fwf3-jfq2

## What is CVE-2026-19380?

CVE-2026-19380 is a medium-severity use after free vulnerability in Mullvad wireguard.sys, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was identified in Mullvad wireguard.sys 0.10.1. The affected element is the function AdapterState of the component IOCTL Handler. Such manipulation leads to improper update of reference count. Local access is required to approach this attack. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure.

Weakness: CWE-911 (Improper Update of Reference Count), CWE-664 (Improper Control of a Resource Through its Lifetime)

## Which versions are affected by CVE-2026-19380?


## How do I fix CVE-2026-19380?

No fix has been published for CVE-2026-19380 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19380 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19380 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19380 and fix it if it is affected.

What it is: CVE-2026-19380 is a medium-severity use after free vulnerability in Mullvad wireguard.sys, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19380 exists.

Affected product: Mullvad wireguard.sys. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19380/ (Markdown: https://insights.sbomify.com/CVE-2026-19380/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19380
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19380
- OSV: https://osv.dev/vulnerability/CVE-2026-19380

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19380/
Summaries are generated and may contain mistakes; the official description above is the record.