CVE-2025-27752
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 · uneditedHeap-based buffer overflow in Microsoft Office Excel 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 confidenceHeap-based buffer overflow vulnerability in Microsoft Office Excel enables local code execution by an unauthorized attacker. The flaw involves memory corruption where data exceeds allocated heap buffer boundaries, potentially allowing an attacker to overwrite memory and inject malicious code.
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.
-
Confirm Microsoft Excel is installedOpen Excel and go to File > Account, or run 'winword --version' if Office is installed alongside Excel, or check Add/Remove Programs for Microsoft ExcelAffected if Excel is present on the system
-
Identify the installed Excel versionIn Excel: File > Account > About Excel. The version number appears in the title bar or About dialog. Alternatively, run 'excel /?' or check registry key HKEY_CLASSES_ROOT\Excel.Application\CurVerAffected if Unable to determine version or version is unclear
-
Compare your version to affected releasesMatch your version number (e.g., 16.0.xxxx for Office 2016/2019/2021 or subscription version for Microsoft 365 Apps) against: Office 2016, Office 2019, Office LTSC 2021, Office LTSC 2024, or any Microsoft 365 Apps versionAffected if Version matches 2016, 2019, 2021, 2024, or is a Microsoft 365 Apps version (all are affected)
-
Verify the vulnerability trigger conditionThis flaw is triggered by opening a specially crafted Excel file (.xlsx, .xlsm, .xlsb). Check recent Excel file opening activity or inspect any suspicious Excel files from untrusted sourcesAffected if User opens or has opened a maliciously crafted Excel file
If Microsoft Excel version 2016, 2019, 2021, 2024, or any Microsoft 365 Apps version is installed and the user opens a specially crafted Excel file, the environment is vulnerable to this CVE.
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 Excel immediately; avoid opening Excel files from untrusted sources; ensure antivirus software is current; consider enabling Protected View in Excel for files from external sources.
- 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-27752 — 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-27752 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