dbcve.org
365 AppsApplication · Microsoft

CVE-2025-26630

HIGH · 7.8 CVSS v3.1 Published 2025-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Use after free in Microsoft Office Access 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

Use After Free vulnerability in Microsoft Office Access allows local attackers to execute arbitrary code by exploiting memory that is accessed after being freed, potentially through maliciously crafted Access database files.

MitigationApply Microsoft security updates for Microsoft Office Access as soon as they become available; prioritize patching systems that process untrusted Access database files.

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 AppsApplication
Affected:all versions
AccessApplication
Affected:= 2016
OfficeApplication
Affected:= 2019
Office Long Term Servicing ChannelApplication
Affected:= 2021= 2024

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. Verify Microsoft Access is installed
    Open Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed Microsoft Office components. Look for entries containing 'Microsoft Access' or 'Access' in the name.
    Affected if Microsoft Access is listed as an installed program
  2. Determine the installed Microsoft Access version
    Open Microsoft Access, click File > Account, and note the version under 'About Access'. Alternatively, run 'reg query "HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration" /v ProductReleaseIds' or check the registry key 'HKLM\SOFTWARE\Microsoft\Office\16.0\Access\InstallRoot' for version information.
    Affected if The displayed version matches any of the affected versions: Access 2016, Office 2019, Office LTSC 2021, Office LTSC 2024, or any Microsoft 365 Apps version
  3. Confirm the Office installation channel
    Run 'reg query HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration /v InstallBranch' or open Access > File > Account to see if it shows 'Microsoft 365' or a named version like 'Office 2019' or 'Office LTSC 2024'.
    Affected if The channel is Microsoft 365 (all versions affected) or matches a named affected version (2016, 2019, 2021, 2024)
  4. Check for pending security updates
    Open Access > File > Account > Update Options > Update Now, or check Windows Update history for recent Microsoft Office security updates. Look for any patches released after the CVE publication date.
    Affected if No recent security updates for Microsoft Office Access have been installed

If Microsoft Access is installed and the version matches any of the affected versions (Access 2016, Office 2019, Office LTSC 2021, Office LTSC 2024, or any Microsoft 365 Apps version) without corresponding security patches, the environment is likely affected by CVE-2025-26630.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security updates for Microsoft Office Access as soon as they become available; prioritize patching systems that process untrusted Access database files.

Recommended fix High confidence
  1. Open Microsoft Word or any Microsoft Office application
  2. Go to File > Account > Update Options > Update Now
  3. Alternatively, open Windows Update (Settings > Update & Security > Windows Update) and check for updates
  4. Install all available Microsoft Office security updates
  5. Restart your computer after installing updates
  6. Verify the update was installed by checking Office version information in File > Account

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

Fix this in 365 Apps Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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