VulnSocial

CVE-2021-41379General(microsoft / windows_10_1507)

MEDIUMCVSS 7.8 · HIGHCISA KEV

Exploit discussion active in current signal (1 latest mentions)

Immediate actions

  • Prioritize remediation for microsoft windows_10_1507 systems immediately
  • Hunt for exploitation attempts and persistence artifacts
  • Increase monitoring for publicly documented tradecraft
  • Track advisory updates for patch or workaround availability

Recommended action window: High priority (within 72h)

NVD description

Windows Installer Elevation of Privilege Vulnerability

microsoft CVEsBack to dashboard
4.0/ 10 priority

Sources & remediation

Listed in the CISA Known Exploited Vulnerabilities catalog. Federal remediation due date: 2022-03-17. Apply updates per vendor instructions.

Patch / fix
Vendor / third-party advisories
Other references
Weakness type (CWE)
CWE-59

Priority

MEDIUM

Exploitation

ACTIVE

PoC

YES

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • windows_10_1507
  • windows_10_1607
  • windows_10_1809
  • windows_10_1909

Threat summary

  • Public PoC and exploit tooling are both present
  • 3 mentions across 2 observed days
  • Momentum state: stable

What's happening

  • Exploit tool or code specified in 1 signal
  • PoC mentioned or linked in 1 signal
  • General: 2 classified signals
  • Peaked 1d ago at 2 mentions (2026-09-11); latest day: 1
  • 3 total mentions across 2 days

Affected systems

Vendors
microsoft
Products
windows_10_1507windows_10_1607windows_10_1809windows_10_1909windows_10_2004windows_10_20h2windows_10_21h1windows_11_21h2windows_7windows_8.1

2 versions affected across 18 products

Deep dive

Activity timeline3 mentions / 2d
01122Mentions · 2026-09-11: 2Mentions · 2026-09-14: 1PoC Mentioned / Linked · 2026-09-14: 1Exploit Tool / Code · 2026-09-14: 109-1109-14
Signal classification2 categories
General
266.7%
Exploit
133.3%
Classification over time
DateTotalLabels
2026-09-112
General2
2026-09-141
Exploit1
Full discourse3 posts
  • Ivan@pumpkineater17
    Exploit

    @Flatlinedixie13 @nudevise @MSNightmare2000 He released exploit for Windows CVE-2021-41379 at his GitHub in Nov2021 when he wasn’t MSFT employee, and didn’t notify MSFT. He explained that MSFT significantly reduced compensation in BugBounty program. Then in 2022 MSFT somehow hired him and who knows what’s happened.

    Post summary

    The tweet highlights the release of an exploit for CVE-2021-41379 on GitHub, mentioning the author's background and Microsoft's BugBounty program changes.

    0003027
    1 followersView on X
  • David@midnight_comms
    General

    can't wait for all the up and coming blogs about CVE-2021-41379

    Post summary

    The statement expresses anticipation for future blog coverage of CVE-2021-41379 but provides no technical, exploit, or mitigation information.

    00010155
    1.1K followersView on X
  • Lalit_m3c4@Lalitbhosale6
    General

    @MSNightmare2000 so you have worked with msrc? cve-2021-41379 was yours ?

    Post summary

    A user is asking @MSNightmare2000 whether they worked with MSRC and if they were responsible for CVE-2021-41379.

    00000958
    54 followersView on X
CPE platform detail20 entries

20 of 20 entries

PartVendorProductVersionTarget SWTarget HW
OSmicrosoftwindows_10_1507---
OSmicrosoftwindows_10_1607---
OSmicrosoftwindows_10_1809---
OSmicrosoftwindows_10_1909---
OSmicrosoftwindows_10_2004---
OSmicrosoftwindows_10_20h2---
OSmicrosoftwindows_10_21h1---
OSmicrosoftwindows_11_21h2---
OSmicrosoftwindows_7---
OSmicrosoftwindows_8.1---
OSmicrosoftwindows_rt_8.1---
OSmicrosoftwindows_server_2004---
OSmicrosoftwindows_server_2008---
OSmicrosoftwindows_server_2008r2-x64
OSmicrosoftwindows_server_2012---
OSmicrosoftwindows_server_2012r2--
OSmicrosoftwindows_server_2016---
OSmicrosoftwindows_server_2019---
OSmicrosoftwindows_server_2022---
OSmicrosoftwindows_server_20h2---

Explore more

Back to dashboardmicrosoft CVEswindows_10_1507 vulnerabilities