CVE-2025-29792
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 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 confidenceUse-after-free vulnerability in Microsoft Office that enables a locally authenticated attacker to escalate privileges by exploiting memory corruption in the Office application process.
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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Check installed Office version via registryOpen Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration, or for MSI installs to HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration. Look for the VersionToReport or Version key.Affected if The reported version matches Microsoft 365 Apps (any version), Office 2016, Office 2019, Office LTSC 2021, or Office LTSC 2024.
-
Check Office executable file versionLocate the core Office application file (such as WINWORD.EXE for Word, EXCEL.EXE for Excel) typically in C:\Program Files\Microsoft Office\root\Office16 or C:\Program Files (x86)\Microsoft Office\root\Office16. Right-click the file, select Properties, and view the Details tab for the Version field.Affected if The file version corresponds to any of the affected versions listed in the CVE.
-
Verify Office update channelIn the same registry path (HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration), check the UpdateChannel value to determine if the installation is receiving regular security updates.Affected if The UpdateChannel is set to a delayed or long-term servicing channel that may delay security patches.
-
Confirm Office processes are runningOpen Task Manager and look for active Microsoft Office processes such as WINWORD.EXE, EXCEL.EXE, POWERPNT.EXE, or OUTLOOK.EXE.Affected if Office applications are actively running, making the memory corruption vulnerability potentially exploitable in that session.
Your environment is affected if you have Microsoft 365 Apps (any version), Office 2016, Office 2019, Office LTSC 2021, or Office LTSC 2024 installed and the software is not patched with the latest Microsoft Office security updates.
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 Office security updates as they become available; prioritize patching systems with local user access given the privilege escalation component.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29792 — 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-29792 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