VulnerabilityPublished 16 Jul 2026Updated 8 Nov 2026

CVE-2026-63089: wg-easy · PRNG

Affects wg-easySource CVE Database V5

Compare

Not known to be exploited · CVSS 9.0 Critical.

Data as of 8 Nov 2026, 14:33 UTC

CVSS 4.0 base score

9.0Critical

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (VulnCheck)	CVSS 4.0	9.0
CNA (VulnCheck)	CVSS 3.1	9.3

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers can reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-07-18.

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:L/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: Present
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: High
Subsequent system integrity: Low
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: High: There is a total loss of confidentiality, resulting in all resources within the Subsequent System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Subsequent system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Subsequent System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
wg-easywg-easy	Affected <=15.3.0	Fixed in–
GitHubwg-easy`pkg:github/wg-easy`Other threats	Affected <=15.3.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available and was implemented in commit 66b292b. Users should upgrade wg-easy to a version including this commit or later to remediate the vulnerability. Until patched, the vulnerability can be exploited due to lack of rate limiting and token expiration validation on the affected endpoint.

Description

CVE-2026-63089 affects wg-easy versions up to 15.3.0 and involves a cryptographically weak pseudo-random number generator used for one-time link token generation. This vulnerability allows unauthenticated attackers to brute-force tokens due to a limited keyspace of 1000 values and lack of rate limiting or token expiration validation. Exploitation enables recovery of WireGuard peer credentials, including PrivateKey and PresharedKey, allowing impersonation of peers on the VPN network. The issue was fixed in commit 66b292b.

Impact

An attacker can recover WireGuard peer credentials by brute-forcing the weakly generated one-time link tokens, leading to unauthorized access and impersonation of VPN peers. This compromises the confidentiality and integrity of the VPN network connections. The vulnerability has a high severity with a CVSS 4.0 score of 9, indicating critical impact on affected systems.

Summary

WireGuard Easy (wg-easy) versions up to 15.3.0 use a weak PRNG for generating one-time link tokens by computing CRC32 over a random value constrained between 0 and 999. The /cnf/:oneTimeLink endpoint does not enforce rate limiting or token expiration checks, enabling unauthenticated network attackers to brute-force tokens with at most 1000 candidates per client ID. Successful brute-forcing allows attackers to retrieve sensitive WireGuard peer credentials (PrivateKey and PresharedKey), facilitating unauthorized VPN peer impersonation. The vulnerability is addressed in commit 66b292b.

References

Community reviews

Loading reviews…