CVE-2025-29811
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 · uneditedImproper input validation in Windows Mobile Broadband 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 confidenceThis is a local privilege escalation vulnerability in Windows Mobile Broadband caused by improper input validation. An attacker who already has authorized access to the system can exploit this flaw to gain higher privileges, potentially achieving administrative or SYSTEM-level access.
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.22621.5189< 10.0.22631.5189< 10.0.26100.3775< 10.0.25398.1551< 10.0.26100.3775CVSS 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 and build numberRun 'winver' or execute 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to display the installed Windows version and build. Alternatively, query the registry with 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild'Affected if The displayed version falls within any of these ranges: Windows 11 22h2 build < 22621.5189, Windows 11 23h2 build < 22631.5189, Windows 11 24h2 build < 26100.3775, Windows Server 2022 23h2 build < 25398.1551, or Windows Server 2025 build < 26100.3775
-
Confirm Windows 11 or Server editionReview the OS Name from the previous step to confirm whether the system is running Windows 11 (any version) or Windows Server 2022/2025Affected if The system is Windows 11 or Windows Server 2022/2025 and the build number is below the patched versions listed above
-
Determine if Mobile Broadband capability is presentCheck for the presence of Mobile Broadband-related components. This can include reviewing installed drivers in Device Manager under 'Network adapters' for Mobile Broadband devices, or checking for the presence of the Windows Mobile Broadband service by reviewing services.msc or running 'get-service | where {$_.DisplayName -like "*Mobile*"}' in PowerShellAffected if Mobile Broadband hardware, driver, or service is present on the system. If Mobile Broadband is not installed or has no associated hardware/service, the attack surface does not apply
A system is affected if it runs a vulnerable Windows 11 or Windows Server 2022/2025 version below the fixed builds AND has Mobile Broadband capability present, allowing a locally authenticated attacker to escalate privileges to SYSTEM level.
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.22621.518910.0.22631.518910.0.25398.1551
Apply the Microsoft security update for CVE-2025-29811 via Windows Update or enterprise patch management systems. Organizations should inventory systems with Mobile Broadband capabilities and prioritize patching those devices.
Windows 11 22h2 to build 10.0.22621.5189 or later | Windows 11 23h2 to build 10.0.22631.5189 or later | Windows 11 24h2 to build 10.0.26100.3775 or later | Windows Server 2022 23h2 to build 10.0.25398.1551 or later | Windows Server 2025 to build 10.0.26100.3775 or later
- Open Settings > System > Windows Update and check for updates
- Install all available Windows updates including the security update for this vulnerability
- Alternatively, manually verify the current build by running 'winver' in the Run dialog
- If the build number is below the fixed version (10.0.22621.5189 for 22h2, 10.0.22631.5189 for 23h2, 10.0.26100.3775 for 24h2/Server 2025, or 10.0.25398.1551 for Server 2022 23h2), download and install the specific KB from the Microsoft Security Response Center (msrc.microsoft.com)
- Restart the system after installing updates
- Verify the fix by checking the installed KB and confirming the build number meets or exceeds the fixed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29811 — 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-29811 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