9.8 CVE-2026-41089

Enriched by CISA Exploit
 

Stack-based buffer overflow in Windows Netlogon allows an unauthorized attacker to execute code over a network.
https://nvd.nist.gov/vuln/detail/CVE-2026-41089

Categories

CWE-121 : Stack-based Buffer Overflow
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). "Stack Overflow" is often used to mean the same thing as stack-based buffer overflow, however it is also used on occasion to mean stack exhaustion, usually a result from an excessively recursive function call. Due to the ambiguity of the term, use of stack overflow to describe either circumstance is discouraged. Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues. Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.) Use tools that are integrated duringcompilation to insert runtime error-checking mechanismsrelated to memory safety errors, such as AddressSanitizer(ASan) for C/C++ [REF-1518]. Use an abstraction library to abstract away risky APIs. Not a complete solution. Implement and perform bounds checking on input. Do not use dangerous functions such as gets. Use safer, equivalent functions which check for boundary errors. Stack-based buffer overflows in SFK for wifi chipset used for IoT/embedded devices, as exploited in the wild per CISA KEV.

References


 

AFFECTED (from MITRE)


Vendor Product Versions
Microsoft Windows Server 2012
  • 6.2.9200.0 < 6.2.9200.26079 [affected]
Microsoft Windows Server 2012 (Server Core installation)
  • 6.2.9200.0 < 6.2.9200.26079 [affected]
Microsoft Windows Server 2012 R2
  • 6.3.9600.0 < 6.3.9600.23181 [affected]
Microsoft Windows Server 2012 R2 (Server Core installation)
  • 6.3.9600.0 < 6.3.9600.23181 [affected]
Microsoft Windows Server 2016
  • 10.0.14393.0 < 10.0.14393.9140 [affected]
Microsoft Windows Server 2016 (Server Core installation)
  • 10.0.14393.0 < 10.0.14393.9140 [affected]
Microsoft Windows Server 2019
  • 10.0.17763.0 < 10.0.17763.8755 [affected]
Microsoft Windows Server 2019 (Server Core installation)
  • 10.0.17763.0 < 10.0.17763.8755 [affected]
Microsoft Windows Server 2022
  • 10.0.20348.0 < 10.0.20348.5139 [affected]
Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)
  • 10.0.25398.0 < 10.0.25398.2330 [affected]
Microsoft Windows Server 2025
  • 10.0.26100.0 < 10.0.26100.32860 [affected]
Microsoft Windows Server 2025 (Server Core installation)
  • 10.0.26100.0 < 10.0.26100.32860 [affected]
© 2022 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation.

CPE

cpe start end
Configuration 1
cpe:2.3:o:microsoft:windows_server_2012:-:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_server_2012:r2:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_server_2016:*:*:*:*:*:*:*:* < 10.0.14393.9140
cpe:2.3:o:microsoft:windows_server_2019:*:*:*:*:*:*:*:* < 10.0.17763.8755
cpe:2.3:o:microsoft:windows_server_2022:*:*:*:*:*:*:*:* < 10.0.20348.5074
cpe:2.3:o:microsoft:windows_server_2022_23h2:*:*:*:*:*:*:*:* < 10.0.25398.2330
cpe:2.3:o:microsoft:windows_server_2025:*:*:*:*:*:*:*:* < 10.0.26100.32772


REMEDIATION




EXPLOITS


Exploit-db.com

id description date
No known exploits

POC Github

Url
https://github.com/0xABCD01/CVE-2026-41089
https://github.com/hnytgl/CVE-2026-41089
https://github.com/ADScanPro/CVE-2026-41089-LongLogon
https://github.com/System32manager/CVE-2026-41089-699
https://github.com/senseibreathhovel/CVE-2026-41089-663
https://github.com/SkySmokeMoat/CVE-2026-41089-552
https://github.com/Planetpliexpose/CVE-2026-41089-277
https://github.com/GalleryJoiner/CVE-2026-41089-686
https://github.com/Mapclaregister/CVE-2026-41089-191
https://github.com/sectiondukestring25/CVE-2026-41089-971
https://github.com/SightFinchFall/CVE-2026-41089-238
https://github.com/raingatorrouter/CVE-2026-41089-953
https://github.com/raingatorrouter/CVE-2026-41089-224
https://github.com/segmentjoninsecret/CVE-2026-41089-334
https://github.com/StampDreamFitting/CVE-2026-41089-986
https://github.com/Powderbatpatch/CVE-2026-41089-397
https://github.com/CrimsonKingfisher/CVE-2026-41089-245
https://github.com/RoyalViceroyBear/CVE-2026-41089-706
https://github.com/SpiralSealFill/CVE-2026-41089-hub
https://github.com/Coasttruvitalize/CVE-2026-41089-latest

Other Nist (github, ...)

Url
No known exploits


CAPEC


Common Attack Pattern Enumerations and Classifications

id description severity
No entry