microsoft windows 11 26h2

Name: microsoft windows 11 26h2
Brand: microsoft

ProduktUS

cpe:2.3:o:microsoft:windows_11_26h2:*:*:*:*:*:*:*:*

Ein im Bedrohungsgraphen erfasstes Produkt; die Schwachstellen unten betreffen es bekanntermaßen.

EPSS ≥ 10%

ungepatcht

nach Schweregrad

29critical378high141medium0low

aktualisiert 2026-10-28

Schwachstellen (548)

Zugehörige CVEs.

Sortierung

ID	Schweregrad	EPSS	ausnutzbar	behoben	veröffentlicht	betroffen
CVE-2026-96951US	high8.8OT kritisch	9.81% (96th)	KEV	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-97798US	high7.8	0.37% (31st)	Exploit	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-83834US	high7.0	0.30% (22nd)	Exploit	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-88091US	high7.8	2.93% (87th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-96186US	high7.8	2.40% (84th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-83855US	high7.5	1.33% (71st)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-105723US	critical9.8	1.32% (71st)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-83795US	high7.5	1.30% (70th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-83860US	high7.5	1.27% (70th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-70031US	high7.5	1.27% (70th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-102217US	high8.8	1.26% (70th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-70170US	medium6.5	1.23% (69th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-87716US	high7.5	1.13% (66th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-85808US	high7.5	1.13% (66th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-84017US	high7.5	1.13% (66th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-103569US	high7.5	1.11% (66th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-100219US	critical9.8	1.10% (66th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-100202US	critical9.8	1.10% (66th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-97814US	critical9.8	1.09% (65th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-97819US	medium6.5	1.08% (65th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-97817US	medium6.5	1.08% (65th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-97813US	medium6.5	1.08% (65th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-70025US	medium6.5	1.08% (65th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-108129US	medium6.5	1.08% (65th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-108128US	medium6.5	1.08% (65th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-108127US	medium6.5	1.08% (65th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-97830US	high7.5	1.07% (65th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-100222US	critical9.8	1.06% (64th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-97805US	critical9.8	1.06% (64th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-83889US	high8.8	1.06% (64th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-96325US	high7.5	1.05% (64th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-70244US	medium6.5	1.04% (64th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-69940US	medium6.5	1.04% (64th)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-85322US	high7.5	1.03% (63rd)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-97816US	critical9.8	1.01% (63rd)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-96924US	critical9.8	1.01% (63rd)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-108467US	high8.8	1.00% (63rd)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-96909US	critical9.8	0.99% (62nd)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-105010US	critical9.8	0.99% (62nd)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-102210US	critical9.8	0.99% (62nd)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-96246US	high7.5	0.98% (62nd)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-96245US	high7.5	0.98% (62nd)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-85334US	high7.5	0.98% (62nd)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-69955US	medium6.5	0.98% (62nd)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-83888US	critical9.8	0.98% (62nd)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-103558US	high7.5	0.98% (62nd)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-108463US	high8.8	0.97% (62nd)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-70024US	critical9.8	0.96% (61st)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-85821US	medium6.5	0.95% (61st)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711
CVE-2026-85331US	medium6.5	0.95% (61st)	—	10.0.26300.9711	2026-10-13	< 10.0.26300.9711

50 von 548 angezeigt

Schwächen (8)

Die Schwächeklassen (CWEs), die die meisten dieser CVEs teilen.

CWE-416Use After Free152 CVEs
CWE-122Heap-based Buffer Overflow112 CVEs
CWE-125Out-of-bounds Read93 CVEs
CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')26 CVEs
CWE-822Untrusted Pointer Dereference22 CVEs
CWE-126Buffer Over-read13 CVEs
CWE-190Integer Overflow or Wraparound13 CVEs
CWE-59Improper Link Resolution Before File Access ('Link Following')11 CVEs

Datenquellen (1)

Welche Quellen diesen Datensatz belegen und wann.

USNVD / CVE548 CVEs

scry

Produkte tragen bekannte Schwachstellen, sobald sie im Internet exponiert sind. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.

Kostenloser Scan