CVE-2025-30381
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 confidenceCVE-2025-30381 is an out-of-bounds read vulnerability in Microsoft Office Excel that allows an unauthorized local attacker to execute arbitrary code. This memory corruption flaw enables code execution through local access, making it a high-severity local privilege escalation issue.
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.20010CVSS 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 application or check for excel.exe process in Task ManagerAffected if Excel is not installed on the system, then not affected
-
Identify installed Excel versionOpen Excel, go to File > Account > About Excel, or run 'excel.exe' from Command Prompt with /? flag to view version infoAffected if Version matches 2016, 2019, 2021, 2024, or falls within Microsoft 365 Apps family
-
Check Office version via registryOpen Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration (for Microsoft 365/Office 2016+) or HKLM\SOFTWARE\Microsoft\Office\<version>\Excel\InstallRoot to find the Version keyAffected if Version number matches affected releases (2016, 2019, 2021, 2024) or is an unpatched Microsoft 365 Apps version
-
For Office Online Server environments, check server versionUse PowerShell Get-OfficeOnlineServerEngine or check the Office Online Server version via the Office Online Server Administration Portal under Server > AboutAffected if Version is lower than 16.0.10417.20010
-
Verify if security update KB number is installedOpen Windows Settings > Update & Security > View update history, or run 'wmic qfe list' from Command Prompt to list installed updates; look for security update related to CVE-2025-30381Affected if No corresponding security update for CVE-2025-30381 is listed in installed updates
A user is affected if Excel is installed with version 2016, 2019, 2021, 2024, or any Microsoft 365 Apps version, and the CVE-2025-30381 security update 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.20010
Apply the Microsoft security update for CVE-2025-30381 as soon as it becomes available through Windows Update or Microsoft Update catalog. Until patched, restrict local access to systems running Excel and consider enabling Protected View for untrusted files.
- 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-30381 — 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-30381 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