Security readout for executives and security teams
Plain-English summary
A locally authorized attacker could abuse Microsoft Defender’s handling of file links to gain higher privileges. Successful exploitation could expose or alter sensitive data and disrupt systems. The vulnerability requires existing local access, but CISA’s Known Exploited Vulnerabilities listing makes remediation urgent.
Executive priority
Treat as an urgent, high-priority endpoint remediation because CISA identifies known exploitation and successful abuse could provide full confidentiality, integrity, and availability impact. Local access limits initial exposure, but compromised low-privilege accounts could become substantially more damaging.
Technical view
CVE-2026-41091 is a CWE-59 link-following flaw in Microsoft Malware Protection Engine. The supplied CVSS 3.1 score is 7.8: local access, low complexity, low privileges, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact.
Likely exposure
The bundle identifies Microsoft Malware Protection Engine version 1.1.0.0 as affected. Exposure outside that exact listed version is not established by the supplied evidence. Prioritize internet-facing, shared, privileged, and high-value endpoints where attackers may already obtain local access.
Exploitation context
CISA’s KEV status supports active exploitation in the wild. Exploitation still requires an authorized attacker with local, low-privilege access; this is not described as a remote initial-access vulnerability. The supplied sources provide no campaign, malware, victim, or exploitation-scale details.
Researcher notes
The weakness is improper link resolution before file access. The bundle does not describe affected paths, timing conditions, corrected engine versions, indicators, or exploit mechanics. Validate scope and fixed-version details directly against Microsoft’s advisory; do not infer additional affected releases from the single supplied version.
Mitigation direction
- Review Microsoft’s CVE advisory for the applicable security update and deployment requirements.
- Apply the Microsoft-provided update across affected systems using an accelerated change window.
- Prioritize endpoints where untrusted or compromised users can obtain local access.
- Restrict unnecessary local accounts and privileges while remediation is pending.
- Use CISA KEV remediation expectations when they apply to your organization.
Validation and detection
- Inventory installed Microsoft Malware Protection Engine versions across managed endpoints.
- Identify systems running the specifically listed affected version, 1.1.0.0.
- Verify successful deployment using the corrected version information in Microsoft’s advisory.
- Confirm Defender remains operational and receives updates after remediation.
- Monitor endpoint telemetry for unexpected privilege elevation and suspicious file-link activity.
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-59: 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 lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior 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-41091 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
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- Yes
- Published
Vector: 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 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.
CISA KEV status
SSVC decision data
CVSS vector scores
1 official scoreWe 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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C1.85.9microsoftVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: 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
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.
- Added to KEVCISA-ADP
CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.
- ADP timelineCISA-ADP
CVE-2026-41091 added to CISA KEV
- 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
- 2026-05-20T00:00:00.000Z: CVE-2026-41091 added to CISA KEV
Source materials
- CVE List V5 sourceCVE List V5
- Microsoft Defender Elevation of Privilege VulnerabilityCVE reference, microsoft · vendor-advisory, patch
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-41091CVE reference, CISA-ADP · government-resource
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.
Improper Link Resolution Before File Access ('Link Following')
Improper Link Resolution Before File Access ('Link Following') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.