On this page (6 sections)

CVE-2026-112967 is a heap-based buffer overflow in the Windows Xbox Live Networking Service. According to the NVD record, it allows an unauthorized attacker to execute code over a network. The record was published on 2026-11-10 with a CVSS score of 9.8, rated critical.

If you manage Windows servers, workstations or images, especially ones built from consumer or gaming-oriented Windows editions, this is worth a quick inventory check. The public information is thin so far, so this article separates what is confirmed from what you still need to verify in Microsoft's own guidance.

What is confirmed so far

The only source in the research is the NVD entry, which gives a one-sentence description: a heap-based buffer overflow in the Windows Xbox Live Networking Service that allows an unauthorized attacker to execute code over a network. The entry lists a CVSS score of 9.8, the weakness identifier CWE-122, and a reference to the Microsoft Security Response Center update guide.

Only one independent publisher covers this story so far. Treat the details here as limited to that record, and expect the picture to change as Microsoft and researchers publish more.

What we do not know yet

  • Which Windows versions and builds are affected.
  • Which update or build number contains the fix, and whether a patch is available.
  • Whether the flaw is being exploited. The NVD record does not say, and the CISA Known Exploited Vulnerabilities data in the research has no entry for it, which is not the same as confirmation that it is unexploited.
  • Whether the vulnerable service is reachable on a default configuration or only when specific features are in use.
  • The CVSS vector, which would show attack complexity and whether user interaction is needed. Only the 9.8 score is given.

Understanding the weakness

A heap-based buffer overflow (CWE-122) happens when a program writes more data into a memory buffer on the heap than the buffer can hold. The extra data spills into neighboring memory and can corrupt it. In the worst cases an attacker who controls that data can steer the program into running their own code.

The description says the attacker is unauthorized and the attack happens over a network. In plain terms, the attacker does not need valid credentials, and the vulnerable code processes data that arrives over the network. That combination is why scores for this kind of flaw land near the top of the scale. It does not by itself tell us how easy the flaw is to trigger in practice.

Who is realistically exposed

The affected component is a Windows service tied to Xbox Live networking. Many server and business systems may not rely on it, but the research does not say which editions include or enable it. Do not assume you are safe because a machine is not used for gaming.

  • Windows desktops and laptops, including managed fleets and kiosks.
  • Windows Server systems and virtual machine templates, if the service is present.
  • Developer, lab and test machines that run consumer Windows editions.
  • Any host where the service is reachable from other network segments or the internet.

If you run websites on Windows hosting, the practical question is whether the underlying host has the service present and what network exposure it has. Ask your hosting provider or check your own servers.

How to check your exposure

Start from Microsoft's advisory, since it is the authoritative source for affected builds and fixes. Then confirm what your systems actually run. The following read-only PowerShell commands show the Windows build and whether a service with Xbox in its display name exists on the machine. Run them in an elevated PowerShell session. For the second command, a listed service means a matching component is present; no output means no service with that name pattern was found.

List the Windows version and build (read-only, run in PowerShell)PowerShell
Get-ComputerInfo -Property WindowsProductName, WindowsVersion, OsBuildNumber
List services with Xbox in the display name and their state (read-only, run in PowerShell)PowerShell
Get-Service | Where-Object { $_.DisplayName -like '*Xbox*' } | Select-Object Name, DisplayName, Status, StartType

Compare the build number against the affected and fixed builds in the Microsoft update guide entry once those are listed there.

What to do now

  1. Open the Microsoft update guide page for CVE-2026-112967 and note the affected products, fixed builds and any mitigations.
  2. Inventory Windows systems and record their build numbers using the check above.
  3. Install the relevant Microsoft security update as soon as it is available for your systems, starting with servers and internet-reachable hosts.
  4. If the service is present but not needed, consider disabling it through your normal change process, after confirming in Microsoft's guidance that this is a supported mitigation.
  5. Restrict inbound network access to Windows hosts to only what is required, using host and network firewalls.
  6. Keep an eye on the NVD and Microsoft entries for updates to exploitation status and affected versions.
Caution. Disabling a service or installing updates can interrupt workloads and may require a restart. Test on a non-production machine first and schedule changes in a maintenance window.

Detection and monitoring

There are no published indicators of compromise in the research, so there is nothing specific to hunt for yet. General good practice still applies: watch for unexpected crashes or restarts of Windows services, unusual inbound connections to hosts that rarely receive them, and new processes spawned by system services.

For the public-facing side of your estate, keep an eye on changes you did not make, such as certificate changes or altered DNS records. Webforta Monitor can alert on certificate, DNS and header changes, which helps you notice unexpected shifts in your external footprint, though it does not detect or block this specific flaw.

For broader habits that reduce the impact of any single vulnerability, such as patch routines, least-privilege access and backups, see the guide on small business website security.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-112967: Heap-based buffer overflow in Windows Xbox Live Networking Service allows an unauthorized attacker to execute code over a network.nvd.nist.gov ·
  • CVE-2026-112967
  • Windows
  • Xbox
  • Remote Code Execution
  • Heap Overflow