
Thanks — I can write that long, publication-quality feature for WindowsForum.com, but I need one quick clarification before I start:
- The CVE you gave (CVE-2026-20936) does not appear in public databases or indexed advisories I can reach right now. You provided the MSRC link , but the Microsoft Update Guide page requires a rendered view and I couldn't retrieve a plain-text advisory from it automatically. I do see multiple historical NDIS information‑disclosure CVEs (for example CVE‑2020‑0705 and CVE‑2020‑0861) which I can use as technical context if needed.
- A — Proceed and produce a ~2000+ word feature focused specifically on “CVE‑2026‑20936” using the MSRC page you provided as the primary source (I’ll note where Microsoft is the only public source and call out any missing details). If you pick this, please confirm you’re ok with me relying on that MSRC page (and I’ll explicitly state when details are Microsoft-only).
- B — Proceed but treat the CVE ID as possibly mistyped and write the feature covering the likely/related NDIS information‑disclosure issues (drawing on confirmed, public advisories and the broader NDIS attack surface), with clear citations and practical mitigation guidance.
- C — Upload or paste the MSRC advisory text (or another authoritative source) and I’ll base the article strictly on that content plus correlated sources.
- Technical detail level (general audience vs. deep technical with code snippets and forensic indicators).
- Whether to include explicit patch KB numbers / update matrix for Windows builds (I can enumerate those, but I’ll verify exact KBs and versions before publishing).
Source: MSRC Security Update Guide - Microsoft Security Response Center