dbcve.org
365 CopilotApplication · Microsoft

CVE-2025-53732

HIGH · 7.8 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 16.0.14326.22618 / 16.0.19127.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
Heap-based buffer overflow 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 confidence

A heap-based buffer overflow vulnerability exists in Microsoft Office that allows an unauthorized local attacker to execute arbitrary code. The vulnerability involves memory corruption where data is written beyond the allocated heap buffer boundaries, potentially enabling code execution with the current user's privileges.

MitigationApply the latest Microsoft Office security updates to address this vulnerability. Ensure regular patch management processes are in place and verify that all Office installations are updated to the patched version.

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 CopilotApplication
Affected:< 16.0.19127.20000
OfficeApplication
Affected:< 16.0.14326.22618

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 product
    Open Programs and Features (appwiz.cpl) or use PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration' -ErrorAction SilentlyContinue | Select-Object ProductReleaseIds
    Affected if Either Microsoft Office or Microsoft 365 Copilot is listed as installed
  2. Check Microsoft Office version
    Open any Office application (Word/Excel/PowerPoint), go to File > Account > About [App] to display the version number, or check the executable properties: right-click WINWORD.EXE/EXCEL.EXE/POWERPNT.EXE in Program Files and view Details tab
    Affected if Version number is below 16.0.14326.22618 (for Microsoft Office) or version cannot be determined (indicating potential older unpatched release)
  3. Check Microsoft 365 Copilot version
    Open any Office application with Copilot enabled, click the Copilot icon to access version info, or check via registry: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Office\Copilot\CurrentVersion' -ErrorAction SilentlyContinue
    Affected if Copilot version is below 16.0.19127.20000 or Copilot is present without a listed version (older unpatched build)
  4. Compare against affected version thresholds
    Document the exact version number found and compare: For Office - must be 16.0.14326.22618 or higher; For Microsoft 365 Copilot - must be 16.0.19127.20000 or higher
    Affected if Installed version falls below the respective threshold for the product in use

If Microsoft Office version is below 16.0.14326.22618 OR Microsoft 365 Copilot version is below 16.0.19127.20000, the environment is affected by this heap-based buffer overflow vulnerability.

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.14326.22618 / 16.0.19127.20000 or later
Fixed in 16.0.14326.2261816.0.19127.20000
Interim mitigation

Apply the latest Microsoft Office security updates to address this vulnerability. Ensure regular patch management processes are in place and verify that all Office installations are updated to the patched version.

Recommended fix High confidence

Microsoft 365 Copilot: version 16.0.19127.20000 or later | Office: version 16.0.14326.22618 or later

  1. Open any Office application (Word, Excel, PowerPoint, etc.)
  2. Go to File > Account > Update Options
  3. Select 'Update Now' to check for and install the latest updates
  4. Alternatively, use Microsoft Update or your organization's patch management system to deploy updates
  5. Verify the installed version by going to File > Account and checking the version number
Caveat Standard Microsoft Office monthly updates typically have minimal breaking changes; enterprise environments should test updates in staging before broad deployment

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

Fix this in 365 Copilot Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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