Xbox Gaming ServicesApplication · Microsoft

CVE-2025-55245

HIGH · 7.8 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 30.104.13001.0 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper link resolution before file access ('link following') in Xbox allows an authorized attacker to elevate privileges locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a local privilege escalation vulnerability in Xbox software where the application improperly resolves symbolic or hard links before accessing files. An authorized attacker with local access can exploit this link-following vulnerability (also known as a TOCTOU race condition) to manipulate file access paths and elevate their privileges to higher permission levels on the system.

MitigationImplement secure file access patterns by canonicalizing all file paths using functions like realpath() before access, validating file ownership and type after opening but before processing, and avoiding following symbolic links in privileged operations. Apply the principle of least privilege to limit the impact of successful exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Xbox Gaming ServicesApplication
Affected:< 30.104.13001.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Find Xbox Gaming Services version via PowerShell
    Run: Get-AppxPackage -Name Microsoft.XboxGamingService | Select-Object Name, Version, PackageFullName
    Affected if Version field shows a number lower than 30.104.13001.0 (e.g., 30.104.12000.0 or earlier)
  2. Check version via registry
    Query registry key: HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModel\StateStore\Package\Microsoft.XboxGamingService* for the Version value
    Affected if Retrieved version is below 30.104.13001.0
  3. Verify Xbox services running in privileged context
    Run: Get-Process | Where-Object {$_.Name -match 'XboxGamingService|XboxGameOverlay'} | Select-Object Name, Id, StartInfo -And check if process runs as SYSTEM or elevated account via: (Get-Process -Name <processname>).StartInfo
    Affected if Xbox Gaming Services process is running with elevated privileges (e.g., as SYSTEM or Administrator)
  4. Check for suspicious symbolic links in Xbox appdata folders
    Inspect folders where Xbox Gaming Services stores data (typically %LOCALAPPDATA%\Packages\Microsoft.XboxGamingService* or %PROGRAMDATA%\Microsoft\Xbox) for any symbolic or hard links created outside normal operation
    Affected if Unexpected symbolic links or hard links exist in Xbox service data directories pointing to sensitive system locations

You are affected if Xbox Gaming Services version is below 30.104.13001.0 AND the service is running with elevated privileges, allowing a local attacker to potentially exploit the TOCTOU link-following vulnerability for privilege escalation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 30.104.13001.0 or later
Fixed in 30.104.13001.0
Interim mitigation

Implement secure file access patterns by canonicalizing all file paths using functions like realpath() before access, validating file ownership and type after opening but before processing, and avoiding following symbolic links in privileged operations. Apply the principle of least privilege to limit the impact of successful exploitation.

Recommended fix High confidence

30.104.13001.0 or later

  1. Open Windows Update and check for available security updates.
  2. Install the update for Xbox Gaming Services to version 30.104.13001.0 or later.
  3. Restart the device if prompted and verify the version in the Xbox app settings.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Xbox Gaming Services Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-55245 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-55245 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data