CVE-2026-55022
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 · uneditedAccess of resource using incompatible type ('type confusion') in Microsoft Office allows an unauthorized attacker to execute code locally.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
Surfaced from public web coverage — external links open in a new tab.
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 · high confidenceA type confusion vulnerability in Microsoft Office allows an unauthorized attacker to execute code locally. The vulnerability stems from accessing a resource using an incompatible type, which can be exploited to achieve code execution on the targeted system.
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 versionsall versionsall versionsall versionsall versionsall versionsCVSS 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.
-
Verify Microsoft Office is installedOpen PowerShell and run: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like '*Microsoft Office*' -or $_.DisplayName -like '*Microsoft 365*'} | Select-Object DisplayName, DisplayVersionAffected if No Office product is found in the registry - the system is not affected because the vulnerable software is not installed
-
Determine the installed Office versionOpen PowerShell and run: Get-ItemProperty 'HKLM:\Software\Microsoft\Office\ClickToRun\Configuration' -ErrorAction SilentlyContinue | Select-Object VersionToReport, PlatformAffected if The version returned matches any of the affected products (Office 2016, 2019, 2021, 2024, or Microsoft 365 Apps) - these versions are vulnerable until patched
-
Check for security update installationOpen PowerShell and run: Get-HotFix | Where-Object {$_.Description -like '*Security*' -and $_.InstalledOn} | Sort-Object InstalledOn -Descending | Select-Object -First 10 Description, InstalledOn, HotFixID. Also check Windows Update history for recent Office security patches.Affected if No recent security update for Office is found, or the last Office security update was released before the CVE patch date - the system may remain vulnerable
-
Verify the specific Office component versionOpen PowerShell and run: (Get-ItemProperty 'HKLM:\Software\Microsoft\Office\*\Common\InstallRoot' -ErrorAction SilentlyContinue).Version. Alternatively, open any Office app, go to File > Account > About [App] to see exact version number.Affected if The displayed version is not the patched version released for this CVE - the system remains vulnerable
If Microsoft Office (any of the listed products) is installed and the security update for this CVE has not been applied, the environment is affected by this type confusion vulnerability that could allow local code execution.
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 dataApply Microsoft Office security updates or patches released for this vulnerability. Verify that all Microsoft Office installations across the environment are updated to the patched version.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-55022 — 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-2026-55022 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