CVE-2025-29791
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 · uneditedAccess of resource using incompatible type ('type confusion') 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 · moderate confidenceA type confusion vulnerability in Microsoft Office allows an unauthorized attacker to execute code locally. The vulnerability stems from accessing a resource using an incompatible type, which can lead to arbitrary code execution when a user opens a specially crafted Office document.
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= 2016= 2019= 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 Microsoft Office versionOpen any Office application (Word, Excel, PowerPoint), go to File > Account, and check the version number under 'About [App]'. Alternatively, open the Microsoft Store app and view installed updates, or use 'winver' command for Windows version, then check Office version via 'コントロール パネル > プログラム > プログラムと機能' to locate Microsoft Office entry.Affected if The installed version matches Microsoft 365 Apps (any version), Office 2016, Office 2019, Office LTSC 2021, or Office LTSC 2024.
-
Confirm Office installation typeCheck if the installation is MSI-based or Click-to-Run by looking at the installation path (C:\Program Files\Microsoft Office\ for MSI, or C:\Program Files\Microsoft Office\root\Office for Click-to-Run). Click-to-Run versions show version info in the Account screen under 'Update Options'.Affected if Office is installed and matches any of the affected versions listed.
-
Verify document handling is enabledOpen a Word document and attempt to view macros or embedded content via File > Info > Inspect Document. Check if Office applications can open and render local files without restrictions.Affected if Office applications can open and process local document files normally, which is the default configuration.
-
Check Protected View statusGo to File > Options > Trust Center > Trust Center Settings > Protected View. Verify whether Protected View is enabled for files from the internet, Outlook attachments, and potentially unsafe locations.Affected if Protected View is disabled or set to 'Enable all' for all three categories, meaning documents from untrusted sources are opened without sandbox protection.
You are affected if you have Microsoft 365 Apps, Office 2016, Office 2019, Office LTSC 2021, or Office LTSC 2024 installed and rely on default document handling without Protected View or Application Guard enabled.
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 Microsoft security updates for Microsoft Office immediately upon release, and consider enabling Protected View or Application Guard for documents from untrusted sources as a defense-in-depth measure.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29791 — 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-29791 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