Description
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.
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | wireguard | No fix yet | — |
| Ubuntu 26.04 LTS | wireguard | No fix yet | — |
| Ubuntu 25.10 | wireguard | No fix yet | — |
| Ubuntu 24.04 LTS | wireguard | No fix yet | — |
| Ubuntu 22.04 LTS | wireguard | No fix yet | — |
Show 3 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 20.04 LTS | wireguard | No fix yet | — |
| Ubuntu 18.04 LTS | wireguard | No fix yet | — |
| Ubuntu 16.04 LTS | wireguard | No fix yet | — |