CVE-2026-99059: Linux kernel · wireguard: noise: reject response consumption after intermediate initiation
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.7 High · fixed in fb5ce4c7790c3eeec820302d08d70ecf46af4295 : patch Linux kernel soon.
Data as of 26 Oct 2026, 13:07 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in fb5ce4c7790c3eeec820302d08d70ecf46af4295, d0305f8d90029556260c6824b61c493c424eba9e, c76a80db593096edf2b3b3972f58b6342a8c6c04 +2
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in specific Linux kernel commits identified by their hashes. Users should update their Linux kernel to a version including these fixes to fully mitigate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.
Description
CVE-2026-99059 is a high-severity vulnerability in the Linux kernel's WireGuard implementation related to the Noise protocol handshake. It involves a race condition where two threads process the same response message concurrently, potentially causing inconsistent handshake state and session derivation. The issue has been fixed in specific Linux kernel commits.
References
- git.kernel.org/stable/c/fb5ce4c7790c3eeec820302d08d70ecf46af4295 (opens in a new tab)
- git.kernel.org/stable/c/c76a80db593096edf2b3b3972f58b6342a8c6c04 (opens in a new tab)
- git.kernel.org/stable/c/4d64a3d6e96aa78619c9c29ffde309794974588a (opens in a new tab)
- git.kernel.org/stable/c/3bec3d32c2a3afd164fc87f95457df2cf9049c20 (opens in a new tab)
- git.kernel.org/stable/c/d0305f8d90029556260c6824b61c493c424eba9e (opens in a new tab)