Microsoft · tun: Require CAP_NET_ADMIN to attach to an ownerless device
Affects MicrosoftSource GCVE Database
Not known to be exploited · CVSS 7.8 High · fixed in ffdf678dd16610e3f006dac904bd37c09684673c : patch Microsoft soon.
Data as of 20 Nov 2026, 08:34 UTC
Thin evidence
One scorer or none| CNA (Linux) | CVSS 3.1 | 7.8 |
|---|
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ffdf678dd16610e3f006dac904bd37c09684673c, e53d1cf05da8ea58a5743b7ce5894fb51b0b9700, e0d98aab41b79b88609f33fb4d8e7a80ab8f648d +1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 Nov 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 19 Nov 2026.
What to do
Upgrade Linux to ffdf678dd16610e3f006dac904bd37c09684673c, e53d1cf05da8ea58a5743b7ce5894fb51b0b9700, e0d98aab41b79b88609f33fb4d8e7a80ab8f648d or 2f92c0286cfd58bff9d6d54c01a771073d5eb775.
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– |
AI-suggested
The absence of known exploits in the wild and lack of patch information indicate that further vendor guidance is needed to determine remediation.
Description
This vulnerability involves the requirement of CAP_NET_ADMIN capability to attach to an ownerless tun device in Microsoft software versions 3.0 and 4.0. The advisory does not provide detailed technical information or impact specifics beyond this requirement change.