1-minute read of a 4 min report

Microsoft FORGE Finds 140 Windows CVEs, Submits 155 Open-Source Reports

By

1-minute read

What a defender needs to know

Microsoft’s FORGE team says its work helped discover 140 Windows CVEs addressed from May through September 2026. In open source, it submitted 155 internally validated reports across 23 projects; maintainers acknowledged or accepted 93 reports across 14 projects or families at the time of writing. The Windows CVEs were addressed in releases; the open-source count measures submitted reports. Microsoft reports that deduplicating repeated scans cut duplicate findings by about 45% in one internal project.

CVE-2026-9545 concerns HTTP/3 early-data request bytes sent before a failed certificate check under the record’s session-cache and early-data conditions. CVE-2026-13608 concerns an incomplete OpenLDAP SASL handshake misread as successful verification. Inventory the libcurl build your application actually loads, identify which feature paths it uses, and move affected branches to the applicable fixed vendor build. The cited Linux kernel CVE-2026-64563 is a local rhashtable walk use-after-free; check the running kernel and distribution backport status before scheduling an update.

For your vulnerability intake, keep the reachable build, reproducer, disposition and owner with each report. Track patch review, regression result and shipped artifact separately from candidate counts. Verify the fixed library or kernel in the deployed build, and run the regression against that build. Without that release check, a large discovery count can mask a queue of unresolved work.

Primary sources