Security readout for executives and security teams
Plain-English summary
WireGuard Easy could generate one-time configuration links with a very small token space. An unauthenticated network attacker who can reach the affected route may recover VPN peer secrets and then impersonate that peer. The provided sources do not show active exploitation or KEV listing.
Executive priority
Treat this as urgent for any internet-reachable wg-easy deployment. Successful exploitation can disclose VPN credentials, enabling unauthorized VPN access and peer impersonation without login.
Technical view
Affected wg-easy versions through 15.3.0 used CRC32 over a random value limited to 0-999 for one-time link tokens. The unauthenticated /cnf/:oneTimeLink route reportedly lacked rate limiting and expiration validation, exposing peer PrivateKey and PresharedKey when a valid token is found.
Likely exposure
Exposure is most likely where wg-easy is reachable from untrusted networks and one-time link configuration retrieval is enabled or accessible. Instances at or before 15.3.0, or before commit 66b292b, should be treated as affected.
Exploitation context
The sources describe unauthenticated remote exploitation with low complexity against a small token space. No source in the bundle states active exploitation in the wild, and the CVE is not marked KEV.
Researcher notes
Evidence comes from the CVE description, GitHub PR, patch commit, and VulnCheck advisory. The affected range is stated as through 15.3.0 and fixed in commit 66b292b. Exploit status is not confirmed by the provided sources.
Mitigation direction
- Upgrade to a wg-easy release containing commit 66b292b or apply the vendor patch.
- Remove public exposure of wg-easy until the patch is deployed.
- Review vendor guidance for any additional mitigations or configuration changes.
- Rotate exposed peer PrivateKey and PresharedKey values after remediation.
- Audit VPN peer activity for suspicious use around exposed one-time links.
Validation and detection
- Inventory all wg-easy deployments and record their running version or commit.
- Confirm whether each instance is through 15.3.0 or before commit 66b292b.
- Check whether the one-time link route is reachable from untrusted networks.
- Verify patched instances no longer use the weak token generation logic.
- Review logs for unexpected configuration retrievals or peer connections.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-338: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-613: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-63089 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N3.94.7VulnCheckCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:L/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9CriticalVector: 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
Base CVSS 3.1 score
9.3CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Pull RequestCVE reference, VulnCheck · issue-tracking
- Patch CommitCVE reference, VulnCheck · patch
- https://www.vulncheck.com/advisories/wireguard-easy-weak-token-generation-information-disclosure-via-otl-routeCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Insufficient Session Expiration
Insufficient Session Expiration represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.