CVE-2025-54898
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 · uneditedOut-of-bounds read 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 confidenceAn out-of-bounds read vulnerability in Microsoft Office Excel enables an unauthorized local attacker to execute arbitrary code. This memory safety flaw allows memory contents to be read beyond allocated buffer boundaries, which can be leveraged to achieve 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= 2024< 16.0.10417.20047CVSS 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.
-
Check installed Excel versionOpen Microsoft Excel, go to File > Account > About Excel to view the version number, or check via Windows Programs and FeaturesAffected if The version shown is 2016, 2019, 2021, or 2024, or if using Microsoft 365 Apps any version before the latest update
-
Check Office product versionOpen any Office application, go to File > Account > About [App Name], or view installed programs in Windows Control Panel > Programs and FeaturesAffected if The installed Microsoft Office version matches 2016, 2019, 2021, or 2024
-
Check Microsoft Office 365 Apps versionOpen any Office app, go to File > Account, and look for the version number under Office Updates, or run: Get-AppxPackage -Name *Microsoft.Office* in PowerShellAffected if The Microsoft 365 Apps version is present and has not been patched for CVE-2025-54898
-
Check Office Online Server versionOn the server, open SharePoint Management Shell and run: Get-SPOWebTemplate to confirm Office Online Server presence, then check version via: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Office\16.0\Common\InstallRoot' | Select-Object VersionAffected if Office Online Server version is lower than 16.0.10417.20047
-
Verify Windows Update patch statusOpen Windows Settings > Update & Security > Windows Update > View update history, or run: wmic qfe list to see installed patchesAffected if No recent security update for Microsoft Office Excel addressing CVE-2025-54898 is listed in the installed updates
You are affected if you have any version of Microsoft Excel 2016, 2019, 2021, or 2024, any version of Microsoft 365 Apps, or Office Online Server before version 16.0.10417.20047, and the corresponding security patch for this CVE is not installed.
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 data16.0.10417.20047
Apply Microsoft security updates for Office Excel immediately upon release through Windows Update or Microsoft Update catalog.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54898 — 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-54898 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