Skip to content
Fencer Intel
high 7.8

CVE-2026-41091 kev in the critical feed json

Microsoft Defender Elevation of Privilege Vulnerability

published 5mo ago modified 2mo ago also EUVD-2026-31101

cvss
7.8
version 3.1, CNA
cisa kev
Exploited
added 2026-05-20
epss
8.2%
EPSS 8.2% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known

Summary

Improper link resolution before file access ('link following') in Microsoft Defender allows an authorized attacker to elevate privileges locally.

Patch / fix

cisa required action Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

  • Microsoft Microsoft Malware Protection Engine 1.1.26040.8

Is CVE-2026-41091 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. CISA SSVC: exploitation active
  2. Added to CISA KEV
  3. Published
  4. CISA patch deadline

Known exploited

Added
5mo ago
Patch by
2026-06-03 (5mo ago)
Ransomware
Not known
Required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Vendor, product
Microsoft, Defender
CISA name
Microsoft Defender Link Following Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
5mo ago

Exploit prediction

8.20% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Microsoft Microsoft Malware Protection Engine

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.