CVE-2026-56192
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 allows an unauthorized attacker to disclose information 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 · moderate confidenceOut-of-bounds read vulnerability in Microsoft Office that allows a local unauthorized attacker to read sensitive information from memory beyond allocated buffer boundaries. The vulnerability has low attack complexity requiring local access and no user interaction, resulting in information disclosure with high confidentiality impact.
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 versions< 16.0.19725.20434= 2016= 2019CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 installation existsCheck the Windows Registry under HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration or HKLM\SOFTWARE\Microsoft\Office\{version}\Common\InstallRoot for installed Office productsAffected if No Office installation is found, the check does not apply. If found, proceed to version check.
-
Retrieve installed Office version and build numberOpen any Office application (Word, Excel, Outlook), go to File > Account > About [App], or run 'winword.exe /about' from Command Prompt to display the exact version and buildAffected if If the displayed build matches any of the affected versions (all versions for Office 2016/2019/2021/2024, Microsoft 365 Apps, or Microsoft 365), the environment is vulnerable.
-
Check SharePoint Server version (if applicable)On the SharePoint server, open SharePoint Management Shell and run: (Get-SPFarm).BuildVersion to get the build number, or check Programs and Features for Microsoft SharePoint Server version 2016 or 2019Affected if If SharePoint Server 2016 or 2019 is installed, or if the build version is less than 16.0.19725.20434, the environment is vulnerable.
-
Confirm patch statusOpen Windows Update > Check for updates, or in Office go to File > Account > Update Options > Update Now to see if updates are available and installedAffected if If updates are available or the last update was before the security patch date for CVE-2026-56192, the environment remains vulnerable.
The environment is affected if Microsoft Office (any version from 2016, 2019, 2021, 2024, or Microsoft 365 Apps) or SharePoint Server (2016, 2019, or build below 16.0.19725.20434) is installed and the corresponding security update for this CVE has not been applied.
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.19725.20434
Apply the latest Microsoft Office security patches and updates. Verify that Microsoft Office is fully patched through standard patch management processes.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56192 — 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-56192 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