CVE-2025-60714
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 Windows OLE 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 confidenceA heap-based buffer overflow vulnerability exists in Windows OLE (Object Linking and Embedding) that allows a local, unauthenticated attacker to execute arbitrary code on the affected system by triggering the overflow through specially crafted OLE objects.
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< 10.0.14393.8594< 10.0.17763.8027< 10.0.19044.6575< 10.0.19045.6575< 10.0.22631.6199all versions= r2all versions= r2< 10.0.14393.8594CVSS 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 Windows build versionOpen Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the exact build numberAffected if The build number falls below the safe thresholds: 14393.8594 (Win10 1607/Server 2016), 17763.8027 (Win10 1809), 19044.6575 (Win10 21h2), 19045.6575 (Win10 22h2), or 22631.6199 (Win11 23h2)
-
Confirm Windows edition for Server 2008/2012Run 'winver' or check System Properties to identify if the system is Windows Server 2008 R2 or Windows Server 2012 R2Affected if The system is Windows Server 2008 (any version including R2) or Windows Server 2012 (any version including R2), as these all versions are affected
-
Verify OLE component presenceCheck for the presence of OLE system DLLs such as 'ole32.dll' or 'oleaut32.dll' in C:\Windows\System32\Affected if The OLE DLLs exist on the system, which is the default state for all supported Windows installations and means the vulnerability is present if the version is unpatched
-
Check for security update installationOpen Control Panel > Programs > View installed updates, or run 'wmic qfe list' in Command Prompt, and look for the February 2025 or later Windows security update containing OLE fixesAffected if The specific CVE-2025-60714 security update is NOT installed and the Windows version falls within the affected build ranges
A system is affected if it runs a Windows version within the affected build ranges and the corresponding security update for CVE-2025-60714 has not been 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.
dbcve · scoped10.0.14393.859410.0.17763.802710.0.19044.6575
Apply the relevant Microsoft security update for Windows OLE to address the heap-based buffer overflow. Prioritize patching systems with direct user access or those exposed to untrusted OLE content.
Microsoft Security Update KB5055527/KB5055518/KB5055523/KB5055519/KB5055525/KB5055520 (specific to Windows version); migrate from EOL Windows Server 2008/2012 to Windows Server 2019/2022
- 1. Identify the Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
- 2. For Windows 10 1607 systems: Apply KB5055527 (build 10.0.14393.8594) or later via Windows Update or Microsoft Update Catalog
- 3. For Windows 10 1809 systems: Apply KB5055518 (build 10.0.17763.8027) or later via Windows Update or Microsoft Update Catalog
- 4. For Windows 10 21h2 systems: Apply KB5055523 (build 10.0.19044.6575) or later via Windows Update or Microsoft Update Catalog
- 5. For Windows 10 22h2 systems: Apply KB5055519 (build 10.0.19045.6575) or later via Windows Update or Microsoft Update Catalog
- 6. For Windows 11 23h2 systems: Apply KB5055525 (build 10.0.22631.6199) or later via Windows Update or Microsoft Update Catalog
- 7. For Windows Server 2016: Apply KB5055520 (build 10.0.14393.8594) or later via Windows Update or Microsoft Update Catalog
- 8. For Windows Server 2008/2012 (all versions): These are end-of-life with no security updates available; migrate to supported Windows Server versions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60714 — 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-60714 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