CVE-2025-27749
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 confidenceA Use After Free (UAF) vulnerability in Microsoft Office allows an attacker to execute arbitrary code locally on the affected system. The vulnerability stems from improper memory management in Office components, where memory is accessed after being freed, potentially leading to controlled 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= 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.
-
Verify Microsoft Office installationCheck for Office installation by querying the registry key HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration (for Microsoft 365/2016+) or looking for Office executables in Program Files (e.g., C:\Program Files\Microsoft Office\root\Office16)Affected if No Office installation found means not affected; if Office is present, proceed to version check
-
Determine installed Office versionRun: reg query 'HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration' /v VersionToReport OR check the file version of WINWORD.EXE (right-click, Properties, Details) in the Office root directoryAffected if Version is Microsoft 365 Apps (any version), Office 2016, Office 2019, Office LTSC 2021, or Office LTSC 2024
-
Confirm affected component presenceVerify the presence of core Office executables: WINWORD.EXE, EXCEL.EXE, OUTLOOK.EXE, POWERPNT.EXE in the Office installation directory - the UAF affects memory handling in these Office componentsAffected if Any of these core Office applications are present and version falls within affected range
-
Check for security update presenceReview installed Windows Updates or check Office update history for patch installation of CVE-2025-27749; in Office, go to File > Account > Update Options > Update HistoryAffected if No security update for CVE-2025-27749 has been installed - this indicates the system remains vulnerable
If Microsoft Office (version 2016, 2019, 2021, 2024, or any Microsoft 365 Apps) is installed and CVE-2025-27749 security update has not been applied, the environment is affected by this Use After Free vulnerability.
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 CVE-2025-27749 immediately. Prioritize patching end-user workstations running Microsoft Office, and verify compatibility in staging before enterprise-wide deployment.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27749 — 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-27749 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