dbcve.org
365 AppsApplication · Microsoft

CVE-2025-30386

HIGH · 7.8 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 16.0.18827.20000 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Use after free in Microsoft Office allows an unauthorized attacker to execute code 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 · low confidence

A use-after-free vulnerability in Microsoft Office allows an attacker to execute arbitrary code locally by manipulating memory that has been freed but not properly cleaned up. This type of memory corruption bug can be triggered through specially crafted Office documents.

MitigationApply Microsoft security updates for Office immediately, ensure all Office installations are patched to the latest version, and consider enabling Protected View for documents from untrusted sources as a defense-in-depth measure.

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
365 AppsApplication
Affected:all versions
365 CopilotApplication
Affected:< 16.0.18827.20000
OfficeApplication
Affected:= 2016= 2019
Office Long Term Servicing ChannelApplication
Affected:= 2021= 2024

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Identify installed Microsoft Office products
    Open Windows Settings > Apps > Apps & features and search for 'Microsoft Office' or 'Microsoft 365'. Alternatively, open Word/Excel/PowerPoint, go to File > Account to see the product name and version.
    Affected if Any Microsoft Office, Microsoft 365 Apps, or Microsoft 365 Copilot product is installed.
  2. Determine Office version number
    Open any Office application (Word, Excel, PowerPoint), click File > Account. Look for the version number displayed (for example, 'Version 2406' or '16.0.xxxxx.xxxxx'). Record this full version string.
    Affected if Version cannot be determined or is not displayed.
  3. Compare 365 Apps version against affected range
    For Microsoft 365 Apps, check if updates are available. Open any Office app > File > Account > Update Options > Update Now. If updates complete successfully, the version will be patched. The affected range is 'all versions' meaning any unpatched version is vulnerable.
    Affected if Microsoft 365 Apps is installed and has not been updated to a version containing the CVE-2025-30386 security patch.
  4. Compare Microsoft 365 Copilot version
    Open Microsoft 365 Copilot application or check version via Windows Settings > Apps. The affected version is below 16.0.18827.20000. Check the exact build number in the app's About or Settings.
    Affected if Microsoft 365 Copilot is installed with version lower than 16.0.18827.20000.
  5. Compare Office 2016/2019 version
    For standalone Office 2016 or 2019, open any Office app > File > Account. The affected versions are specifically = 2016 and = 2019 (exact version matches). Check if the installed version matches these specific releases.
    Affected if Office 2016 or 2019 is installed and matches the exact affected version numbers.
  6. Compare Office LTSC 2021/2024 version
    For Office Long Term Servicing Channel, open any Office app > File > Account. The affected versions are = 2021 and = 2024 (exact version matches). Verify the exact build against these releases.
    Affected if Office LTSC 2021 or 2024 is installed and matches the exact affected version numbers.

If any Microsoft Office product is installed and has not been updated with the CVE-2025-30386 security patch, the environment is potentially affected. Microsoft 365 Apps has no specific version boundary (all versions unpatched are vulnerable), while standalone Office versions have specific affected releases.

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

Apply Microsoft security updates for Office immediately, ensure all Office installations are patched to the latest version, and consider enabling Protected View for documents from untrusted sources as a defense-in-depth measure.

Recommended fix Moderate confidence

Microsoft 365: version 16.0.18827.20000 or later; Office LTSC 2024: install latest security patches; Office LTSC 2021: install latest security patches; Office 2019/2016: install latest security patches

  1. Verify your current Microsoft Office version by opening any Office app, going to File > Account > About [App]
  2. For Microsoft 365 Copilot users: Update to version 16.0.18827.20000 or later via File > Account > Update Options > Update Now
  3. For Microsoft 365 Apps: Ensure automatic updates are enabled or manually check for updates via File > Account > Update Options > Update Now
  4. For Office LTSC 2021/2024 and Office 2016/2019: Install the latest security updates from Microsoft Update (Windows Update) or the Microsoft Update Catalog
  5. Restart all Office applications after updating
Caveat Standard update - no major breaking changes expected for security patches

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

Fix this in 365 Apps Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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