VulnSocial

CVE-2026-42907Patch(microsoft / windows_10_1809)

LOWCVSS 6.5 · MEDIUM

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch microsoft windows_10_1809 systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

Exposure of sensitive information to an unauthorized actor in Windows Shell allows an authorized attacker to disclose information over a network.

microsoft CVEsBack to dashboard
1.0/ 10 priority

Sources & remediation

Vendor / third-party advisories
Weakness type (CWE)
CWE-200

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

Are you affected?

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

  • windows_10_1809
  • windows_10_21h2
  • windows_10_22h2
  • windows_11_23h2

Threat summary

  • Patch or workaround signal is available
  • 1 mentions across 1 observed day

What's happening

  • Patch or workaround mentioned in 1 signal
  • 1 total mentions across 1 day

Affected systems

Vendors
microsoft
Products
windows_10_1809windows_10_21h2windows_10_22h2windows_11_23h2windows_11_24h2windows_11_25h2windows_11_26h1windows_server_2019windows_server_2022windows_server_2025

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-06-10: 1Patch / Workaround · 2026-06-10: 106-10
Signal classification1 categories
Patch
1100.0%
Referenced assets1 URL
Full discourse1 post
  • WindowsForum@windowsforum
    Patch

    🪟 Another Windows Shell info disclosure… but the real villain is patch timing. Medium bugs become chaos when they’re weaponized fast. Microsoft says “June Patch Tuesday,” attackers say “thank you.” #Windows #Microsoft #Security #CVE https://windowsforum.com/threads/cve-2026-42907-why-a-windows-shell-info-disclosure-patch-timing-matters.424798/?utm_source=x&utm_medium=social&utm_campaign=news_node84 #InformationDisclos… https://t.co/Uan7C1kEwQ

    Post summary

    The tweet highlights concerns about the timing of the June Patch Tuesday release for CVE‑2026‑42907, implying that delays could enable attackers to weaponize the vulnerability.

    0000037
    1.2K followersView on X
CPE platform detail19 entries

19 of 19 entries

PartVendorProductVersionTarget SWTarget HW
OSmicrosoftwindows_10_1809--x64
OSmicrosoftwindows_10_1809--x86
OSmicrosoftwindows_10_21h2--arm64
OSmicrosoftwindows_10_21h2--x64
OSmicrosoftwindows_10_21h2--x86
OSmicrosoftwindows_10_22h2--arm64
OSmicrosoftwindows_10_22h2--x64
OSmicrosoftwindows_10_22h2--x86
OSmicrosoftwindows_11_23h2--arm64
OSmicrosoftwindows_11_23h2--x64
OSmicrosoftwindows_11_24h2--arm64
OSmicrosoftwindows_11_24h2--x64
OSmicrosoftwindows_11_25h2--arm64
OSmicrosoftwindows_11_25h2--x64
OSmicrosoftwindows_11_26h1--arm64
OSmicrosoftwindows_11_26h1--x64
OSmicrosoftwindows_server_2019---
OSmicrosoftwindows_server_2022---
OSmicrosoftwindows_server_2025--x64

Explore more

Back to dashboardmicrosoft CVEswindows_10_1809 vulnerabilities