CVE-2021-46873General(microsoft / windows)

LOWCVSS 5.3 · MEDIUM

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD 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.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-362

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • windows
  • wireguard

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • Technical details provided in 1 signal
  • General: 1 classified signal
  • 1 total mentions across 1 day

Affected systems

Products
windowswireguard

2 versions affected across 2 products

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-04-10: 1Technical Details · 2026-04-10: 104-10
Signal classification1 categories
General
1100.0%
Full discourse1 post
  • Miloš van DotNET ✡︎@msdevelx
    General

    Do you really have to ask so primitively like this is some random toy app and not a security critical VPN tool that sat completely dead for over four years with zero updates? Fine. There was CVE-2023-35838 in the old 0.5.3 version. The firewall rules were set up like shit and let an attacker on the local network force your machine to block local traffic even when the VPN was fully running. Not exactly a great look for a VPN right? There was also CVE-2021-46873 where someone could fuck with the system time and permanently kill your static private keys. But honestly the CVEs are the smallest part of it. The real issue is four straight years of total neglect. No compatibility fixes for new Windows versions (a ton of people were screwed on 11 24H2), no Go runtime security bumps, no performance or MTU improvements nothing at all even though all that work was sitting ready in the repo the whole time.

    Post summary

    The text briefly mentions two CVEs with rough technical details but focuses more on the software’s prolonged lack of updates and broader security negligence.

    00030335
    58 followersView on X
CPE platform detail2 entries

2 of 2 entries

PartVendorProductVersionTarget SWTarget HW
OSmicrosoftwindows---
Appwireguardwireguard0.5.3--

Explore more