CVE-2025-24067
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 · uneditedHeap-based buffer overflow in Microsoft Streaming Service 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 confidenceA heap-based buffer overflow vulnerability exists in Microsoft Streaming Service that allows a locally authenticated attacker with existing authorization to execute arbitrary code with elevated privileges. The vulnerability stems from improper bounds checking when handling data in the heap memory region.
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< 10.0.10240.20947< 10.0.14393.7876< 10.0.17763.7009< 10.0.19044.5608< 10.0.19045.5608< 10.0.22621.5039< 10.0.22631.5039< 10.0.26100.3403> 10.0.26100.3403, < 10.0.26100.3476CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows version against affected rangesRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"' and compare the Build number to the affected version list. For Windows 10 1507 look for Build < 10240.20947, for 1607 look for < 14393.7876, for 1809 look for < 17763.7009, for 21h2 look for < 19044.5608, for 22h2 look for < 19045.5608. For Windows 11 22h2 look for < 22621.5039, for 23h2 look for < 22631.5039, for 24h2 look for versions < 26100.3403 or between 26100.3404 and 26100.3475.Affected if The installed Windows version falls within any of the version ranges listed in the CVE (versions before the fixed builds, or specific ranges for Windows 11 24h2).
-
Identify if Microsoft Streaming Service is presentRun 'Get-Service | Where-Object {$_.DisplayName -like "*Streaming*"}' in PowerShell, or run 'sc query type= service state= all' and search for any service with "Streaming" in the name or description.Affected if The Microsoft Streaming Service is found installed on the system.
-
Check if the streaming service is runningRun 'Get-Service -Name *Streaming* -ErrorAction SilentlyContinue' or 'sc query <service_name>' (replace with the streaming service name found in the previous step) to check the service status.Affected if The Microsoft Streaming Service is in a Running state.
-
Verify user context and local authentication accessConfirm that the account being assessed has local authentication privileges on the system (standard user or administrator). This vulnerability requires a locally authenticated attacker with existing authorization.Affected if The account has local logon capability to the system, which is typical for most user accounts.
A system is likely affected if it runs any of the listed Windows versions with the Microsoft Streaming Service present and running, as the heap-based buffer overflow can then be exploited by a locally authenticated attacker to execute code with elevated privileges.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.10240.2094710.0.14393.787610.0.17763.7009
Apply the appropriate Microsoft security updates for Microsoft Streaming Service once released, and ensure systems are patched through standard Windows Update or enterprise patch management processes.
Windows Security Update for CVE-2025-24067 (KB specific to your Windows version) - Fixed versions: Win10 1507: 10.0.10240.20947 | Win10 1607: 10.0.14393.7876 | Win10 1809: 10.0.17763.7009 | Win10 21h2: 10.0.19044.5608 | Win10 22h2: 10.0.19045.5608 | Win11 22h2: 10.0.22621.5039 | Win11 23h2: 10.0.226
- 1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
- 2. Determine which version bracket your system falls into from the affected versions list
- 3. Apply the appropriate Windows Security Update (KB) for your specific Windows version that includes the fix for CVE-2025-24067
- 4. Alternatively, enable Automatic Updates and ensure all pending security updates are installed
- 5. Restart the system after applying the update
- 6. Verify the fix by checking the installed Windows version matches or exceeds the fixed version number for your release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24067 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24067 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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