dbcve.org
365 AppsApplication · Microsoft

CVE-2025-59226

HIGH · 7.8 CVSS v3.1 Published 2025-10-14
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 Visio 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 use-after-free memory corruption vulnerability in Microsoft Office Visio allows a local attacker to achieve code execution by exploiting improperly freed memory objects. The vulnerability stems from the software failing to properly manage memory lifecycle, enabling an attacker to inject and execute arbitrary code in the context of the current user.

MitigationApply the latest Microsoft security updates for Microsoft Office Visio as soon as practicable; prioritize patching given the local code execution capability and HIGH severity rating.

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
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. Confirm Visio installation
    Check if Microsoft Visio is installed by reviewing installed programs: Open Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration, or run 'Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration -ErrorAction SilentlyContinue | Select-Object Platform, VersionToReport' in PowerShell
    Affected if Visio is not installed on the system (not vulnerable in that case)
  2. Identify Microsoft 365 Apps version
    For Microsoft 365 Apps, check the version from the ClickToRun registry key: Run 'Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration -ErrorAction SilentlyContinue | Select-Object VersionToReport' in PowerShell
    Affected if Any non-zero version number is returned (all Microsoft 365 Apps versions are affected)
  3. Identify LTSC Office version
    For Office LTSC (Long Term Servicing Channel), check the version at HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration or HKLM\SOFTWARE\Microsoft\Office\16.0\Common\InstallRoot for Office 2021, or the corresponding 17.0 key for Office 2024
    Affected if The installed version equals 2021 or 2024 (exact match required per the affected versions)
  4. Verify Visio component presence
    Confirm the Visio executable exists: Check for C:\Program Files\Microsoft Office\root\OfficeXX\VISIO.EXE or C:\Program Files (x86)\Microsoft Office\root\OfficeXX\VISIO.EXE where XX is the Office version number (e.g., 16 for Office 2021, 17 for Office 2024)
    Affected if The VISIO.EXE file exists and matches an affected Office/Visio version

The system is affected if Microsoft Visio is installed and the installed version falls under Microsoft 365 Apps (any version) or Office LTSC versions 2021 or 2024.

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 the latest Microsoft security updates for Microsoft Office Visio as soon as practicable; prioritize patching given the local code execution capability and HIGH severity rating.

Recommended fix Moderate confidence
  1. Open Microsoft Word or any Microsoft 365 application to access the account settings
  2. Go to File > Account > Update Options > Update Now to check for and install the latest Microsoft updates
  3. Alternatively, open Windows Update (Settings > Update & Security > Windows Update) and check for updates to install all pending Microsoft Office security patches
  4. For Office Long Term Servicing Channel (2021 or 2024), use the Office Deployment Tool or check the Microsoft Update Catalog for the specific security update KB article associated with CVE-2025-59226
  5. After applying updates, verify the Visio version by opening Visio > File > Account > About Visio to confirm the patch was applied

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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 locally
dbcve dependency scanner

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