CVE-2025-55677
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 · uneditedUntrusted pointer dereference in Windows Device Association Broker 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 confidenceAn untrusted pointer dereference vulnerability in the Windows Device Association Broker service allows a local authorized attacker to execute code with elevated privileges by manipulating pointer references that the service trusts without proper validation.
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.26100.6899< 10.0.26200.6899< 10.0.26100.6899CVSS 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 build versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build numberAffected if Build number is less than 10.0.26100.6899 for 24h2/Server 2025, or less than 10.0.26200.6899 for 25h2
-
Verify Windows editionRun 'winver' or check System Properties to confirm the Windows edition (Windows 11 24h2, Windows 11 25h2, or Windows Server 2025)Affected if Running an affected edition and the build number falls below the corresponding threshold
-
Confirm Device Association Broker service existsRun 'sc query DeviceAssociationBroker' or check Services.msc for the Device Association Broker serviceAffected if The service exists on the system (service name typically DeviceAssociationBroker or DeviceAssociationBrokerSvc)
A system is affected if it runs Windows 11 24h2, Windows 11 25h2, or Windows Server 2025 with a build number below the respective threshold and the Device Association Broker service is present.
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.26100.689910.0.26200.6899
Apply the Microsoft security update for CVE-2025-55677 to all affected Windows systems; as this is a local privilege escalation, prioritize patching endpoints and restrict local administrative access where possible.
Windows 11 24h2: build 10.0.26100.6899 or later | Windows 11 25h2: build 10.0.26200.6899 or later | Windows Server 2025: build 10.0.26100.6899 or later
- Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
- Confirm the build number is below 10.0.26100.6899 (for Win11 24h2/Server 2025) or below 10.0.26200.6899 (for Win11 25h2)
- Backup critical data before applying updates
- Open Settings > Windows Update and check for updates, or run 'wuauclt /detectnow'
- Install all available security updates including the KB for CVE-2025-55677
- Reboot the system when prompted
- Verify the update was applied by checking the new build number matches or exceeds 10.0.26100.6899
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55677 — 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-55677 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