Abstract illustration of connected devices separated by a protected security boundary.
When enterprise system administrators scan a security bulletin queue and spot the word "Xbox" in an advisory heading, the natural reflex is to keep scrolling. After all, data center racks rarely host late-night multiplayer sessions. Yet Microsoft Security Response Center (MSRC) advisory data for CVE-2026-78455, titled Xbox Information Disclosure Vulnerability, is a pointed reminder that Xbox components live directly inside the Windows operating system—spanning desktop editions of Windows 10 and Windows 11 as well as Windows Server 2016 and Windows Server 2019. Rated Important by Microsoft, this flaw stems from an out-of-bounds read (CWE-125) capable of exposing kernel memory during a physical attack, making patch verification essential across both client fleets and affected server baselines.

Abstract illustration of connected devices separated by a protected security boundary. Advisory Snapshot and Official MSRC Telemetry​

Before diving into how a physical-access memory read changes risk calculations on shared workstations and kiosks, IT teams need the exact baseline telemetry published by Microsoft in its official Security Update Guide entry for CVE-2026-78455:

  • CVE ID: CVE-2026-78455
  • Vulnerability Title: Xbox Information Disclosure Vulnerability
  • Severity: Important
  • CVSS Base Score: 4.3
  • CVSS Temporal Score: 3.8
  • CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C
  • Weakness Classification: CWE-125
  • Official Description: Out-of-bounds read in Xbox allows an unauthorized attacker to disclose information with a physical attack.
  • Exploitation Assessment: Exploitation Less Likely
  • Publicly disclosed: No
  • Exploited: No
  • Customer action required: Yes

Microsoft's official advisory documentation highlights two core facts that clarify both the mechanism and the target data at risk:

  1. Xbox Information Disclosure Vulnerability: Out-of-bounds read in Xbox allows an unauthorized attacker to disclose information with a physical attack.
  2. Kernel Memory Information Disclosure: Addressing what type of information could be disclosed by this vulnerability, Microsoft states that exploiting this vulnerability could allow the disclosure of certain kernel memory content.

Section Summary: CVE-2026-78455 is an Important-severity CWE-125 out-of-bounds read in Xbox components shipped across affected Windows client and server platforms, carrying a 4.3 CVSS base score (3.8 temporal) and requiring customer patching despite having no active exploitation or prior public disclosure.


Decoding the Technical Risk: CWE-125, Physical Vectors, and Kernel Memory​

Why would a vulnerability carrying a seemingly modest CVSS base score of 4.3 still earn an Important severity rating from Microsoft? Synthesizing from general industry knowledge of the Common Vulnerability Scoring System (CVSS v3.1) and Windows kernel architecture helps explain that apparent contradiction.

Looking closely at the official vector string—CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C—reveals the exact trade-offs shaping the score:

  • Attack Vector — Physical (AV:P): Unlike network-borne exploits that can sweep across open ports from halfway around the globe, a physical attack vector requires hands-on interaction with the target machine or its hardware interfaces. That physical prerequisite heavily depresses the numerical CVSS score.
  • Attack Complexity — Low (AC:L) and Privileges Required — None (PR:N): Once physical access is achieved, the attacker does not need an authenticated local user account or complex race-condition gymnastics to trigger the flaw.
  • User Interaction — Required (UI:R): Successful exploitation depends on user interaction on the target system alongside the physical attack path.
  • Confidentiality Impact — High (C:H), Integrity — None (I:N), Availability — None (A:N): The vulnerability does not directly modify system memory or trigger a denial-of-service crash on its own, but the confidentiality impact within the component's scope (S:U) is rated High.
  • Temporal Modifiers (E:U/RL:O/RC:C): Unproven exploit maturity (E:U), an official fix (RL:O), and confirmed report confidence (RC:C) bring the temporal score to 3.8.

From a general systems-security perspective, CWE-125 (Out-of-bounds Read) occurs when software reads memory past the end—or before the beginning—of an intended buffer because boundary checks are missing or miscalculated. When that unchecked read touches kernel memory, the stakes rise considerably. Kernel space holds privileged operating system structures, memory pointers, and operational data isolated from standard processes. Even when an out-of-bounds read cannot execute arbitrary code by itself, security researchers and red teams routinely prize kernel memory disclosures because leaked memory addresses can help defeat Kernel Address Space Layout Randomization (KASLR) when chained with separate flaws.

Think of it like someone slipping an inspection camera under a vault door: they haven't unlocked the deadbolt yet, and they still had to walk right up to the door in person, right? True—which is why Microsoft assesses the flaw as Exploitation Less Likely. Still, in environments with public-facing PCs, hotel business centers, university labs, retail point-of-sale terminals, shared conference-room PCs, or branch-office servers sitting in unlocked closets, physical proximity is far easier to come by than inside a badge-controlled data hall.

Section Summary: While the physical attack vector (AV:P) and required user interaction (UI:R) keep the CVSS base score at 4.3, the ability to read beyond buffer boundaries (CWE-125) and expose certain kernel memory content justifies treating the patch as a mandatory baseline update—especially for physically accessible endpoints.


Complete Affected Products, KB Packages, and Fixed Builds​

A critical takeaway from MSRC's affected-product matrix is breadth. CVE-2026-78455 spans x86, x64, and ARM64 editions across Windows 10 and Windows 11, alongside full and Server Core installations of Windows Server 2016 and Windows Server 2019. Notice that shared servicing branches consolidate several operating system releases under six cumulative update packages: KB5123099, KB5122876, KB5122878, KB5122880, KB5124008, and KB5124012.

Affected ProductRequired UpdateFixed Build
Windows 10 Version 1607 for 32-bit Systems (x86)KB512309910.0.14393.9512
Windows 10 Version 1607 for x64-based SystemsKB512309910.0.14393.9512
Windows 10 Version 1809 for 32-bit Systems (x86)KB512287610.0.17763.9245
Windows 10 Version 1809 for x64-based SystemsKB512287610.0.17763.9245
Windows 10 Version 21H2 for 32-bit Systems (x86)KB512287810.0.19044.7725
Windows 10 Version 21H2 for ARM64-based SystemsKB512287810.0.19044.7725
Windows 10 Version 21H2 for x64-based SystemsKB512287810.0.19044.7725
Windows 10 Version 22H2 for 32-bit Systems (x86)KB512287810.0.19045.7725
Windows 10 Version 22H2 for ARM64-based SystemsKB512287810.0.19045.7725
Windows 10 Version 22H2 for x64-based SystemsKB512287810.0.19045.7725
Windows 11 Version 23H2 for ARM64-based SystemsKB512288010.0.22631.7582
Windows 11 Version 23H2 for x64-based SystemsKB512288010.0.22631.7582
Windows 11 Version 24H2 for ARM64-based SystemsKB512400810.0.26100.9445
Windows 11 Version 24H2 for x64-based SystemsKB512400810.0.26100.9445
Windows 11 Version 25H2 for ARM64-based SystemsKB512400810.0.26200.9445
Windows 11 Version 25H2 for x64-based SystemsKB512400810.0.26200.9445
Windows 11 Version 26H1 for ARM64-based SystemsKB512401210.0.28000.2954
Windows 11 version 26H1 for x64-based SystemsKB512401210.0.28000.2954
Windows Server 2016 (Server Core installation) (x64)KB512309910.0.14393.9512
Windows Server 2016 (x64)KB512309910.0.14393.9512
Windows Server 2019 (Server Core installation) (x64)KB512287610.0.17763.9245
Windows Server 2019 (x64)KB512287610.0.17763.9245

Official Platform-by-Platform Remediation Requirements​

To close CVE-2026-78455 across every listed configuration, administrators must apply the exact update corresponding to each operating system and architecture:

  • For Windows 10 Version 1607 for 32-bit Systems (x86), install KB5123099 to reach fixed build 10.0.14393.9512.
  • For Windows 10 Version 1607 for x64-based Systems, install KB5123099 to reach fixed build 10.0.14393.9512.
  • For Windows 10 Version 1809 for 32-bit Systems (x86), install KB5122876 to reach fixed build 10.0.17763.9245.
  • For Windows 10 Version 1809 for x64-based Systems, install KB5122876 to reach fixed build 10.0.17763.9245.
  • For Windows 10 Version 21H2 for 32-bit Systems (x86), install KB5122878 to reach fixed build 10.0.19044.7725.
  • For Windows 10 Version 21H2 for ARM64-based Systems, install KB5122878 to reach fixed build 10.0.19044.7725.
  • For Windows 10 Version 21H2 for x64-based Systems, install KB5122878 to reach fixed build 10.0.19044.7725.
  • For Windows 10 Version 22H2 for 32-bit Systems (x86), install KB5122878 to reach fixed build 10.0.19045.7725.
  • For Windows 10 Version 22H2 for ARM64-based Systems, install KB5122878 to reach fixed build 10.0.19045.7725.
  • For Windows 10 Version 22H2 for x64-based Systems, install KB5122878 to reach fixed build 10.0.19045.7725.
  • For Windows 11 Version 23H2 for ARM64-based Systems, install KB5122880 to reach fixed build 10.0.22631.7582.
  • For Windows 11 Version 23H2 for x64-based Systems, install KB5122880 to reach fixed build 10.0.22631.7582.
  • For Windows 11 Version 24H2 for ARM64-based Systems, install KB5124008 to reach fixed build 10.0.26100.9445.
  • For Windows 11 Version 24H2 for x64-based Systems, install KB5124008 to reach fixed build 10.0.26100.9445.
  • For Windows 11 Version 25H2 for ARM64-based Systems, install KB5124008 to reach fixed build 10.0.26200.9445.
  • For Windows 11 Version 25H2 for x64-based Systems, install KB5124008 to reach fixed build 10.0.26200.9445.
  • For Windows 11 Version 26H1 for ARM64-based Systems, install KB5124012 to reach fixed build 10.0.28000.2954.
  • For Windows 11 version 26H1 for x64-based Systems, install KB5124012 to reach fixed build 10.0.28000.2954.
  • For Windows Server 2016 (Server Core installation) (x64), install KB5123099 to reach fixed build 10.0.14393.9512.
  • For Windows Server 2016 (x64), install KB5123099 to reach fixed build 10.0.14393.9512.
  • For Windows Server 2019 (Server Core installation) (x64), install KB5122876 to reach fixed build 10.0.17763.9245.
  • For Windows Server 2019 (x64), install KB5122876 to reach fixed build 10.0.17763.9245.

Section Summary: Twenty-two distinct Windows 10, Windows 11, and Windows Server product configurations require one of six Microsoft security updates (KB5123099, KB5122876, KB5122878, KB5122880, KB5124008, or KB5124012) to reach their respective fixed build thresholds.


Practical Guidance for Windows Admins and Everyday Users​

Because Customer action required: Yes applies across every affected edition—including headless Server Core deployments of Windows Server 2016 and Windows Server 2019—relying on title-based filtering in patch management workflows is a classic pitfall. Based on standard Windows administration practices, IT teams and home users can streamline rollout and verification in three straightforward steps:

  1. Prioritize Physically Exposed Endpoints First: While cumulative Microsoft security patches naturally roll out across entire update rings, devices in lobbies, classrooms, retail counters, field vehicles, and coworking spaces face real-world exposure to AV:P scenarios. Move those groups into early deployment waves.
  2. Audit Build Numbers Rather Than Guessing by Component Name: Do not assume that uninstalling consumer gaming apps or running Server Core removes underlying OS-level Xbox components. Verify compliance directly against the fixed build numbers listed above—such as 10.0.26100.9445 or 10.0.26200.9445 after installing KB5124008, or 10.0.17763.9245 after installing KB5122876—using winver on desktop systems or Get-ComputerInfo and Get-HotFix in PowerShell on Server Core installations.
  3. Reinforce Physical Port and Access Hygiene: Alongside installing the official security updates, standard defense-in-depth measures—locking unattended workstations, restricting physical access to branch-office server racks, and enforcing peripheral access controls—help blunt physical-vector attacks before an attacker can prompt user interaction.

For readers tracking broader Windows 11 updates, legacy Windows 10 servicing, or server hardening discussions here on WindowsForum.com, CVE-2026-78455 serves as another textbook example of modular OS realities: under the hood of Windows, components with consumer-sounding names often share deep architectural roots across workstation and server editions alike. Checking your build number takes thirty seconds—and keeps your kernel memory strictly to yourself.

 

References

  1. Official MSRC or vendor evidence msrc.microsoft.com
  2. Official MSRC or vendor evidence api.msrc.microsoft.com
  3. Official MSRC or vendor evidence api.msrc.microsoft.com