InfraGuard

Port 51820 (WireGuard) — exposure risk

A standard public service — usually fine to expose, but keep it patched and on TLS.

StandardVPN

What it is

Secure tunnels such as OpenVPN, IPsec, WireGuard.

Why it is risky

Public by design, but outdated protocols (PPTP) and unpatched gateways become an entry path.

What to do

Keep protocols/patches current, enforce MFA, and retire PPTP.

Is it listening on your server?

Linuxss -ltnp 'sport = :51820'

Known vulnerabilities in WireGuard

CVE Title CVSS Exploited EPSS Published
CVE-2023-35838 The WireGuard client 0.5.3 on Windows insecurely configures the operating system and firewall such that traffi... 5.7 — 2023-08-09
CVE-2021-46873 WireGuard, such as WireGuard 0.5.3 on Windows, does not fully account for the possibility that an adversary mi... 5.3 — 2023-01-29

All WireGuard vulnerabilities →

Track these versions on your own servers

InfraGuard collects installed software versions from every server and flags the ones with known vulnerabilities. Self-hosted — nothing leaves your network.

Weekly exploited-vulnerability digest

The KEV additions that matter for self-hosted servers, once a week. No other mail.