dbcve.org
Defender For EndpointApplication · Microsoft

CVE-2025-47161

HIGH · 7.8 CVSS v3.1 Published 2025-05-15
Fix available
A fix is available. Upgrade to 101.25022.0002 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 access control in Microsoft Defender for Endpoint 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

Improper access control vulnerability in Microsoft Defender for Endpoint enables a locally authenticated attacker with existing authorized access to escalate privileges to higher permission levels on the affected system.

MitigationDeploy the Microsoft security update for CVE-2025-47161 through Windows Update or organizational patch management, then verify Microsoft Defender for Endpoint continues functioning properly.

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
Defender For EndpointApplication
Affected:< 101.25022.0002

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. Verify Microsoft Defender for Endpoint is installed
    Open Windows Security app > Settings > About, or run 'Get-MpComputerStatus' in PowerShell and check for 'AntivirusEnabled' or 'AntispywareEnabled' properties
    Affected if Microsoft Defender for Endpoint is not present on the system (not applicable)
  2. Retrieve the installed Microsoft Defender for Endpoint version
    Run 'Get-MpComputerStatus' in PowerShell and locate the 'AntivirusSignatureVersion' or 'AntivirusEngineVersion' field, OR check the Microsoft Defender for Endpoint security intelligence version in Windows Security > Settings > About
    Affected if Cannot retrieve a version number (Defender for Endpoint may not be fully deployed)
  3. Compare installed version against affected range
    Note the full version number from the previous step and compare numerically to 101.25022.0002. The version format is typically major.minor.build.revision (for example, 101.23061.0002)
    Affected if The installed version number is lower than 101.25022.0002 (for example, 101.23061.0002 or 101.24012.0001)
  4. Confirm the system is joined to a managed environment
    Verify the device is onboarded to Microsoft Defender for Endpoint by checking Windows Security > Device security > Tenant onboarding status, or by running 'msiexec /i' with the onboarding package and checking if registration succeeds
    Affected if Device is not properly onboarded (vulnerability may still exist but attacker would need different initial access)

The environment is affected if Microsoft Defender for Endpoint is installed and onboarded with a version number lower than 101.25022.0002.

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 101.25022.0002 or later
Fixed in 101.25022.0002
Interim mitigation

Deploy the Microsoft security update for CVE-2025-47161 through Windows Update or organizational patch management, then verify Microsoft Defender for Endpoint continues functioning properly.

Recommended fix Moderate confidence

Microsoft Defender for Endpoint version 101.25022.0002 or later

  1. Open Microsoft Defender for Endpoint Security Settings
  2. Navigate to the version information or about section
  3. Check the current installed version of Defender for Endpoint
  4. If version is below 101.25022.0002, initiate the update process
  5. Apply the update through your organization's endpoint management solution or automatic updates
  6. Verify the version has been updated to 101.25022.0002 or later after the update completes
Caveat Updates to Microsoft Defender for Endpoint typically occur automatically through Windows Update; verify compatibility with your organization's endpoint protection policies before manual deployment

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

Fix this in Defender For Endpoint Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47161 — 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-47161 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