Patch & vulnerability status
WireGuard LLC
WireGuard 1.0.16
Latest tracked version 1.0.16. Release status, tracked CVEs, and automated cross-platform patching for WireGuard.
Category: VPN and Zero Trust
| Platform | Latest version | CVEs tracked | Last checked |
|---|---|---|---|
| Mac | 1.0.16 | 2 | 2026-08-10 |
| Windows | 1.1 | 0 | 2026-08-10 |
Known vulnerabilities (CVEs) in WireGuard
Lavawall tracks 2 published CVEs affecting WireGuard, and deploys the versions that fix them automatically across your fleet.
| CVE | Published | Severity | Details | Vector |
|---|---|---|---|---|
| CVE-2023-35838 | 2023-08-09 23:15:10 | MEDIUM (6) | The WireGuard client 0.5.3 on Windows insecurely configures the operating system and firewall such that traffic to a local network that uses non-RFC1918 IP addresses is blocked. This allows an adversary to trick the victim into blocking IP traffic to selected IP addresses and services even while the VPN is enabled. NOTE: the tunnelcrack.mathyvanhoef.com website uses this CVE ID to refer more generally to "LocalNet attack resulting in the blocking of traffic" rather than to only WireGuard. | ADJACENT_NETWORK |
| CVE-2021-46873 | 2023-01-29 23:15:09 | MEDIUM (5) | WireGuard, such as WireGuard 0.5.3 on Windows, does not fully account for the possibility that an adversary might be able to set a victim's system time to a future value, e.g., because unauthenticated NTP is used. This can lead to an outcome in which one static private key becomes permanently useless. | NETWORK |
Why keeping WireGuard patched matters
Unpatched third-party applications are one of the most common ways attackers get in: 57% of breached MSP clients and 32% of ransomware cases trace back to a missing patch. Every WireGuard release that fixes a security bug is public, so attackers see it too, and an out-of-date install becomes a documented way in. Tracking the installed version on every machine and closing the gap quickly is what turns a disclosed CVE into a non-event.
How Lavawall® patches WireGuard
Lavawall® watches WireGuard releases and CVEs continuously, ranks each update by risk, and deploys it across your whole fleet, Windows, macOS, and Linux, from a single agent, independently of your RMM. You get one place to see which machines are behind on WireGuard, one policy to bring them current, and timestamped evidence for audits.
Frequently asked questions
Lavawall tracks WireGuard at version 1.0.16 (last checked 2026-08-10). New releases are monitored continuously and can be deployed automatically across your fleet.
Lavawall tracks 2 CVEs for WireGuard and remediates them automatically as part of patching.
Deploy the Lavawall® agent and WireGuard updates are applied automatically across Windows, macOS, and Linux, risk-ranked and reported, independently of your RMM.
Lavawall® monitors releases and CVEs for WireGuard through public information and proprietary statistical analysis, and can patch it automatically across your fleet.