CVE-2025-62216
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 · uneditedUse 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 confidenceUse-after-free vulnerability in Microsoft Office allows an attacker to execute arbitrary code locally. This memory corruption issue occurs when the software continues to use memory after it has been freed, potentially leading to code execution.
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 dataall versions= 2021= 2024CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Office product typeOpen any Office application (Word, Excel, PowerPoint), go to File > Account. Look for the product name which will display as either 'Microsoft 365' (indicating Microsoft 365 Apps) or a year such as 'Office LTSC 2021' or 'Office LTSC 2024'Affected if The installed product is Microsoft 365 Apps, Office LTSC 2021, or Office LTSC 2024
-
Determine exact Office version numberIn the same Account screen, click 'About [AppName]' to view the full version and build number. Alternatively, open Command Prompt and run: winword /? or excel /? to see version informationAffected if Version cannot be determined or shows as any version of the affected products listed above
-
Check if Protected View is enabledGo to File > Options > Trust Center > Trust Center Settings > Protected View. Verify whether documents from internet locations and Outlook attachments open in Protected ViewAffected if Protected View is disabled and the user opens untrusted Office documents
-
Verify macro execution settingsGo to File > Options > Trust Center > Trust Center Settings > Macro Settings. Check the current setting for enabling or disabling macros in documentsAffected if Macros are set to 'Enable all macros' or similar permissive setting
If the environment runs Microsoft 365 Apps, Office LTSC 2021, or Office LTSC 2024 and has not yet received a security update addressing this use-after-free flaw, the system is potentially affected.
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.
From vendor dataApply latest Microsoft Office security updates when available. Until a patch is released, exercise caution with Office documents from untrusted sources and consider enabling protected view settings.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62216 — 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-62216 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