CVERadar
MEDIUM · CVSS 3.1 5.5Public PoCEPSS 0.43% (p38)Threat level 32

CVE-2026-83681: CVE-2026-83681: Weak authentication in Microsoft PowerToys allows an authorized attacker to perform tamper…

Unknown · Weak · NVD published 2026-10-14 · posted 2026-10-13 · last modified 2026-10-23

CVE-2026-83681 at a glance

CVE-2026-83681 is a medium-severity vulnerability in Weak, with a CVSS 3.1 base score of 5.5. NVD published it on 2026-10-14 and classifies the weakness as CWE-1390. Public exploit code: 1 public GitHub proof-of-concept repository from 1 account, with the earliest exploit evidence dated 2026-10-13. FIRST EPSS puts the probability of exploitation activity in the next 30 days at 0.43% (percentile 37.8, scored 2026-11-10). NVD does not list a fixed version, so the vendor advisory is the reference for the fix. Its CVERadar threat level is 32/100.

What it is

Weak authentication in Microsoft PowerToys allows an authorized attacker to perform tampering locally.

WeaknessCWE-1390 definition
CVSS vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N (source: Microsoft)
ATT&CK tacticsn/a

Exploitation evidence

First exploit evidence seen: 2026-10-13 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

GitHub proof-of-concept repositories

1 public repositories from 1 accounts, first seen 2026-10-13. Most starred: 2alf/CarbonBlue (27 stars), view the 2alf/CarbonBlue repository on GitHub.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: nomi-sec/PoC-in-GitHub.

Patches, mitigations and detection

Fixed versions

NVD does not list a fixed version for this CVE. Use the vendor advisory below.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

No vendor-tagged reference yet; see the full reference list.

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    Sources