dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-30194

HIGH · 7.5 CVSS v3.1 Published 2022-08-09
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
Remotely reachable Zero-click

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
Windows WebBrowser Control Remote Code Execution Vulnerability

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

This is a remote code execution vulnerability in the Windows WebBrowser Control (MSHTML/Trident rendering engine). The vulnerability allows attackers to execute arbitrary code on affected Windows systems through malicious web content rendered by the WebBrowser Control.

MitigationApply Microsoft security updates released for this vulnerability; disable or restrict the WebBrowser Control in applications where possible; implement network-level filtering to block malicious content.

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
Windows 10Operating system
Affected:all versions= 20h2= 21h1= 1607= 1809
Windows 11Operating system
Affected:all versions
Windows 7Operating system
Affected:all versions
Windows 8.1Operating system
Affected:all versions
Windows Rt 8.1Operating system
Affected:all versions
Windows Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:all versions= 20h2

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
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/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. Check if the security update is installed
    Open PowerShell and run: Get-HotFix -Id 'KB5015019' (or search for 'KB5015021' for server versions). Alternatively, check Windows Update history for June 2022 cumulative updates.
    Affected if The hotfix or June 2022 cumulative update is NOT installed and the system is a supported Windows version listed as affected.
  2. Identify applications using WebBrowser Control
    Check running processes for applications known to embed the WebBrowser Control: Outlook, Word, Excel, PowerPoint, Lync, Skype for Business, Microsoft Teams (legacy), and custom applications using the COM component '8856f961-340a-11d0-a96b-00c04fd705a2'. Use Process Explorer or query registered COM clients with reg query 'HKLM\SOFTWARE\Classes\WOW6432Node\CLSID\{8856f961-340a-11d0-a96b-00c04fd705a2}\InprocServer32'.
    Affected if Any application using the WebBrowser Control is present and the system lacks the security update.
  3. Verify Trident/MSHTML engine version
    Open Internet Explorer (if present) or check the MSHTML.dll version. Run: powershell (Get-Item 'C:\Windows\System32\mshtml.dll').VersionInfo.FileVersion. Compare against the patched version (approximately 11.0.22000.0 or higher for Windows 11).
    Affected if The MSHTML.dll version is below the patched version released June 2022.
  4. Check for recent Trident/MSHTML-based attacks
    Review Windows Event Viewer for suspicious mshta.exe, cscript.exe, or wscript.exe executions spawning from Office applications (especially Outlook, Word, Excel). Check Security event logs for process creation events (Event ID 4688) with unusual parent-child relationships.
    Affected if Suspicious script execution originating from Office or other WebBrowser Control-hosting applications is observed.

The environment is affected if any system runs an unpatched Windows version from the affected list AND hosts applications that utilize the WebBrowser Control (such as Office applications, Outlook, or custom apps), enabling malicious web content to execute code.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security updates released for this vulnerability; disable or restrict the WebBrowser Control in applications where possible; implement network-level filtering to block malicious content.

Fix this in Windows 10 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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