dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-49690

HIGH · 7.4 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.17763.7558 / 10.0.19044.6093 or later.
See remediation →
79/100
Remediation priority · High
No privileges 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
Concurrent execution using shared resource with improper synchronization ('race condition') in Capability Access Management Service (camsvc) allows an unauthorized 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 race condition vulnerability in the Capability Access Management Service (camsvc) where improper synchronization allows an attacker to manipulate shared resources during concurrent execution. The flaw enables local privilege escalation by exploiting timing windows in the service's access control logic.

MitigationApply vendor patches for camsvc and review synchronization mechanisms (locks, mutexes, atomic operations) in the affected service code to ensure proper handling of concurrent operations.

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
Windows 10 1809Operating system
Affected:< 10.0.17763.7558
Windows 10 21h2Operating system
Affected:< 10.0.19044.6093
Windows 10 22h2Operating system
Affected:< 10.0.19045.6093
Windows 11 22h2Operating system
Affected:< 10.0.22621.5624
Windows 11 23h2Operating system
Affected:< 10.0.22631.5624
Windows 11 24h2Operating system
Affected:< 10.0.26100.4652
Windows Server 2019Operating system
Affected:< 10.0.17763.7558
Windows Server 2022Operating system
Affected:< 10.0.20348.3932

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:N/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. Check Windows build number
    Run `winver` or `systeminfo | findstr /B /C:"OS Version"` to obtain the full build number including the revision (e.g., 10.0.19045.6093)
    Affected if The build number is lower than the affected threshold for your Windows version (e.g., < 10.0.17763.7558 for Windows 10 1809/Server 2019, < 10.0.19044.6093 for Windows 10 21h2, < 10.0.19045.6093 for Windows 10 22h2, < 10.0.22621.5624 for Windows 11 22h2, < 10.0.22631.5624 for Windows 11 23h2, < 10.0.
  2. Identify Windows edition and version branch
    Run `winver` or check System Properties to confirm whether you are on Windows 10 1809, 21h2, 22h2, Windows 11 22h2/23h2/24h2, Windows Server 2019, or Windows Server 2022
    Affected if The system matches any of the affected Windows editions listed in the CVE
  3. Verify camsvc service presence
    Run `Get-Service -Name camsvc` or `sc query camsvc` to check if the Capability Access Management Service is installed and running on the system
    Affected if The camsvc service exists and is running (vulnerability only applies when this service is present and active)

You are affected if your Windows build number falls below the version-specific threshold for your Windows edition AND the camsvc service is present on the system.

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 10.0.17763.7558 / 10.0.19044.6093 / 10.0.19045.6093 or later
Fixed in 10.0.17763.755810.0.19044.609310.0.19045.6093
Interim mitigation

Apply vendor patches for camsvc and review synchronization mechanisms (locks, mutexes, atomic operations) in the affected service code to ensure proper handling of concurrent operations.

Recommended fix High confidence

Install the appropriate Windows cumulative update for your version (May 2025 Patch Tuesday or later) containing KB50xxxxx that addresses CVE-2025-49690

  1. Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Settings > Windows Update > Check for updates
  3. Install all available cumulative updates for your Windows version
  4. After installation, verify the build number matches or exceeds the fixed version: Windows 10 1809/Server 2019: 10.0.17763.7558, Windows 10 21h2: 10.0.19044.6093, Windows 10 22h2: 10.0.19045.6093, Windows 11 22h2: 10.0.22621.5624, Windows 11 23h2: 10.0.22631.5624, Windows 11 24h2: 10.0.26100.4652, Windows Server 2022: 10.0.20348.3932
  5. Restart the system when prompted to complete the update installation
Caveat Standard Windows update risks apply - ensure backups and test in non-production environments before broad deployment

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

Fix this in Windows 10 1809 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-49690 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-49690 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