← Back to Feed CACHED · 2026-09-16 01:09:05 · CACHE_KEY CVE-2026-51990
CVE-2026-51990 · CWE-74 · Disclosed 2026-04-09

Sogou Input Method biz_helper.exe Protocol Handler Remote Code Execution

ASSESSED — NOISGATE
Vendor
—
—
—
Reassessed
—
—
—
Verdict: —
Do you agree?
01 · The Real Story

Your keyboard helper has a six-year-old browser engine with no locks on the doors, and someone already walked in

CVE-2026-51990 is a remote code execution vulnerability in Tencent's Sogou Input Method for Windows, affecting all versions prior to 16.3.0.3498. The flaw chains three weaknesses: (1) unvalidated command-line argument injection in the sgbiz: custom URI protocol handler (biz_helper.exe), (2) unrestricted URL navigation in a CEF-based webview that accepts any scheme with no domain allowlist, and (3) an embedded Chromium 80 engine (March 2020 vintage) running with sandbox explicitly disabled and same-origin policy turned off. A single click on a crafted sgbiz: link triggers biz_helper.exe → SGMyInput.exe → SGWebRender.exe, which loads an attacker-controlled webpage in the unsandboxed browser. The attacker then exploits CVE-2021-38003 (a V8 type confusion in JSON.stringify) to achieve arbitrary code execution, downloads a legitimate 7-Zip binary alongside a trojanized DLL, and sideloads the GrayRabbit backdoor. Sogou Input Method commands roughly 55% of China's third-party input method market — hundreds of millions of Windows installations.

No vendor CVSS score has been published. Given the 1-click attack surface, the active in-the-wild exploitation by UNC3569 (a PRC-nexus espionage group), and the fact that the patch only addresses the protocol handler without fixing the underlying unsandboxed Chromium engine, this vulnerability warrants a HIGH assessment at 8.0. It falls short of CRITICAL because (a) it requires user interaction (clicking a link), (b) the blast radius is limited to the host where Sogou is installed, (c) the affected software is a desktop IME — not infrastructure — so it does not occupy a high-value role that would trigger the CRITICAL floor, and (d) in Western enterprise environments the installed base is narrow. However, for any organization with Chinese-language workstations, this is an urgent priority.

"One-click RCE in Sogou IME actively exploited by Chinese APT to drop GrayRabbit backdoor"
02 · The Attack Path

5 steps from start to impact.

STEP 01

Deliver crafted sgbiz: URI

The attacker sends a spearphishing email or instant message containing a crafted sgbiz:sg_process?module=sgmyinput.exe&param=... link. The param value URL-encodes a -page=skincenter -url=https://attacker.tld/payload.html argument string. No special tooling is required — the link is a standard URI. UNC3569 campaigns used links pointing to noht1ng[.]top.
Conditions required:
  • Target has Sogou Input Method installed
  • Target's OS has the sgbiz: protocol handler registered
  • Attacker can deliver a link to the target (email, IM, web)
Where this breaks in practice:
  • Standard email gateway / URL filtering may flag unknown domains
  • Link requires the user to actively click — no drive-by
Detection/coverage: Email gateways can match sgbiz: scheme in message bodies. EDR process telemetry will show biz_helper.exe spawning with attacker-controlled arguments.
STEP 02

Protocol handler launches unsandboxed browser

Windows dispatches the sgbiz: URI to biz_helper.exe, which validates the module parameter but passes param directly — after a single URL decode — as command-line arguments to SGMyInput.exe. The skincenter page creates a CEF webview using -url with zero validation: no scheme check, no domain allowlist. The webview initializes SGWebRender.exe backed by Chromium 80 with no_sandbox=TRUE and disable-web-security hardcoded.
Conditions required:
  • Step 1 succeeded — user clicked the link
  • Sogou version < 16.3.0.3498
Where this breaks in practice:
  • Application control (WDAC/AppLocker) policies blocking unsigned child processes from Sogou directory would break the chain
  • Host-based firewall blocking outbound from SGWebRender.exe stops payload fetch
Detection/coverage: EDR should flag SGWebRender.exe or SGMyInput.exe launching with a -url parameter pointing to a non-Sogou/non-Tencent domain.
STEP 03

V8 type confusion exploit fires

The attacker-hosted page delivers JavaScript exploiting CVE-2021-38003, a V8 type confusion in JSON.stringify affecting Chrome < 95. In the unsandboxed Chromium 80 context, this yields arbitrary read/write on the heap. The exploit locates WebAssembly instances backed by RWX memory pages, overwrites executable pages with shellcode, and jumps into it — achieving native code execution as the current user with no additional privilege escalation required.
Conditions required:
  • Step 2 succeeded — attacker page loaded in unsandboxed Chromium 80
  • No browser-level exploit mitigations (sandbox is off, SOP is off)
Where this breaks in practice:
  • Exploit is for a specific V8 version — Chromium 80's V8 must be compatible with the PoC (it is, since the bug predates Chrome 95)
  • Network-layer TLS inspection may detect or block the exploit page
Detection/coverage: Memory-corruption exploit artifacts may trigger EDR heuristics. Network IDS signatures for CVE-2021-38003 exploit patterns could match.
STEP 04

Shellcode downloads and sideloads GrayRabbit

The shellcode downloads three files from a staging server (8.218.50[.]207 on Alibaba Cloud HK): a legitimate 7z.exe, a trojanized 7zp.dll (saved as 7z.dll), and an encrypted payload p. These are written to C:\Users\Public\Documents\. The legitimate 7-Zip binary sideloads the malicious DLL, which performs anti-sandbox checks (process count > 50), XOR-decrypts the payload, and reflectively loads core.dll (GrayRabbit) via thread pool execution.
Conditions required:
  • Step 3 succeeded — shellcode is running
  • Outbound connectivity to staging server on port 443
Where this breaks in practice:
  • Application control would block execution of unsigned binaries from Public\Documents
  • EDR DLL sideloading detection should flag 7z.exe loading a non-standard 7z.dll
  • Anti-sandbox gate (process count < 50) may prevent detonation in thin VDI images
Detection/coverage: EDR: unsigned DLL loaded by 7z.exe from user-writable path. YARA: SHA256 29c7ee41d0cc9e07d981e451df56d0c3d37c41ac4ec10c7b516cc033ee397a63 for the trojanized loader.
STEP 05

GrayRabbit establishes C2

The backdoor (core.dll) beacons to mail.uaiubifas[.]top over TCP port 443 using RC4 encryption (static key m5b1u3) in 0x1000-byte frames. It supports 10 commands: silent process execution, interactive reverse shell, file upload, system enumeration (hostname, username, IPv4, PID), reflective plugin loading, and self-termination. The plugin architecture allows the operator to extend capabilities at runtime without touching disk.
Conditions required:
  • Step 4 succeeded — GrayRabbit loaded in memory
  • Outbound TCP 443 to C2 domain resolves and is reachable
Where this breaks in practice:
  • DNS sinkholing or blocking of known IOC domains stops C2
  • Network monitoring for TCP 443 traffic without valid TLS handshake is a strong detection signal
  • Endpoint isolation post-detection severs the channel
Detection/coverage: Network: flag TCP 443 connections lacking a proper TLS ClientHello. DNS: block mail.uaiubifas[.]top and noht1ng[.]top. Snort/Suricata rules for RC4-framed non-TLS traffic on 443.
03 · Compensating Control

1
Block or remove the sgbiz: protocol handler via registry — Delete or deny HKCR\sgbiz and HKCU\Software\Classes\sgbiz registry keys to sever the attack's entry point. This breaks Sogou's built-in skin marketplace and promotional features but does not affect core typing functionality. Deploy within 30 days per the noisgate mitigation SLA for HIGH severity.
2
Deploy application control (WDAC / AppLocker) rules — Block execution of unsigned binaries from C:\Users\Public\Documents\ and restrict SGWebRender.exe from spawning child processes. This breaks the DLL sideloading step even if the protocol handler is exploited. Deploy within 30 days.
3
Add IOC domains and IPs to DNS sinkhole and firewall blocklists — Block noht1ng[.]top, mail.uaiubifas[.]top, and 8.218.50[.]207 at the DNS resolver and egress firewall. This disrupts both exploit delivery and C2 for the known UNC3569 campaign. Deploy immediately.
4
Restrict outbound connections from Sogou processes — Use host firewall rules (Windows Firewall, EDR network containment) to limit SGWebRender.exe, biz_helper.exe, and SGMyInput.exe to Tencent/Sogou CDN domains only. This prevents the embedded browser from reaching attacker infrastructure.
5
Replace Sogou with Windows native Microsoft Pinyin IME — For environments where Sogou is not a business-critical requirement, migrating to the built-in Windows IME eliminates the attack surface entirely. Evaluate feasibility within the 30-day mitigation window.
What doesn't work
  • Network-level TLS inspection alone — the V8 exploit payload is delivered over HTTPS and may be obfuscated; inspection engines are unlikely to detect the JavaScript exploit reliably without specific signatures.
  • Patching to 16.3.0.3498 without additional controls — while the patch blocks the known attack vector, the underlying Chromium 80 engine remains unsandboxed with web-security disabled. A domain allowlist bypass or a new -url injection vector reopens the chain. Treat the patch as necessary but insufficient.
  • Antivirus signature-only detection — GrayRabbit uses reflective PE loading and NTFS alternate data streams for self-deletion; traditional file-based AV will miss the in-memory payload.
04 · Intelligence Metadata

The supporting signals.

In-the-Wild ExploitationActive. UNC3569 (PRC-nexus espionage group, per Google Threat Intelligence) observed deploying GrayRabbit backdoor against government, education, technology, and finance targets in East and Southeast Asia.
Proof of ConceptNo standalone public PoC for the Sogou protocol handler chain. The V8 component leverages the well-known CVE-2021-38003 PoC (STAR Labs). The full weaponized chain was documented by Gen Threat Labs with a sample sgbiz: URI.
EPSSNot yet scored by FIRST (CVE published September 10, 2026). Given active exploitation, expect rapid climb once indexed.
KEV StatusNot listed as of 2026-09-16. CISA KEV coverage of non-US-centric consumer software is historically limited.
CVSS Vector (noisgate estimate)CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H — Network-reachable, low complexity, no privileges required, user interaction required (click), high CIA impact. Estimated 8.8 on the vendor scale; noisgate adjusts to 8.0 accounting for required social engineering and narrow enterprise footprint.
Affected VersionsSogou Input Method for Windows < 16.3.0.3498. All prior versions ship with the vulnerable biz_helper.exe protocol handler and unsandboxed Chromium 80.
Fixed Version16.3.0.3498 (released April 21, 2026 via auto-update). Patch restricts -url / -firsturl switches to HTTPS and four approved domains (sogou.com, qq.com, woa.com, sogou). Does NOT re-enable sandbox or update Chromium.
Scanning / Exposure DataSogou Input Method holds ~55% of China's third-party IME market. Estimated 500M+ Windows installations. Enterprise exposure outside Greater China is low but non-zero — any org with Chinese-language workstations or subsidiaries in APAC should assume exposure.
Disclosure Timeline2026-04-09: Gen Threat Labs reports to Tencent. 2026-04-21: Tencent ships v16.3.0.3498. 2026-09-10: Gen Threat Labs publishes full technical writeup. 2026-09-14: SecurityWeek / BleepingComputer coverage.
Reporting ResearcherGen Threat Labs (discovery and full chain analysis). Google Threat Intelligence (UNC3569 attribution and campaign tracking).

Sources.

  1. Gen Threat Labs — Full Technical Writeup
  2. BleepingComputer — GrayRabbit Campaign Coverage
  3. SecurityWeek — Chinese Hackers Exploit Tencent Flaw
  4. The Hacker News — UNC3569 Sogou Exploitation
  5. Security Online — CVE-2026-51990 Exploited in the Wild
  6. Security Arsenal — Detection and Remediation Guide
  7. Rescana — Targeted Attack Analysis
05 · The Call

Final Verdict
= UNCHANGED to HIGH (8.0/10)

Why this verdict

  • Active APT exploitation: UNC3569 is using this in live espionage campaigns targeting government, education, tech, and finance in East/Southeast Asia — this is not theoretical.
  • 1-click, no-auth RCE: The chain requires only that a user click a link. No authentication, no prior access, no elevated privileges. Attack complexity is low once the link is delivered.
  • Massive consumer install base: ~500M+ Windows installations in China. For any enterprise with APAC operations, Chinese-language subsidiaries, or a diaspora workforce, Sogou is likely present on workstations.
  • Incomplete patch: Version 16.3.0.3498 addresses the protocol handler input validation but leaves the unsandboxed Chromium 80 engine intact — future bypasses against the domain allowlist or new V8 exploits remain viable.
  • Role multiplier: Sogou IME runs on end-user workstations (low-value role). It is not a domain controller, hypervisor, identity provider, or infrastructure component. The chain ends at host-level code execution as the logged-in user. Lateral movement to high-value targets requires additional post-exploitation steps outside this CVE's scope. The worst plausible outcome is workstation compromise → credential theft → pivot, but that second hop is not intrinsic to this vulnerability. No high-value role floor applies.

Why not higher?

The vulnerability requires user interaction — the target must click a crafted link, which introduces a social-engineering dependency that prevents fully autonomous exploitation. Sogou IME is a desktop application, not a high-value infrastructure component (not a DC, hypervisor, IdP, or network edge device), so the blast radius is limited to the individual host. The CRITICAL floor does not trigger because the affected component does not canonically occupy a high-value role.

Why not lower?

Active exploitation by a resourced APT group with a documented backdoor deployment pipeline eliminates any argument for MEDIUM or below. The 1-click attack surface with no authentication requirement and the enormous install base (500M+ in China) mean the friction is genuinely low for targeted campaigns. The incomplete nature of the patch — Chromium 80 remains unsandboxed — means the fix is fragile and future exploitation variants are likely.

06 · Verification

Crowdsourced verification payload.

Run on each Windows host where Sogou may be installed. Execute in an elevated PowerShell session: powershell -ExecutionPolicy Bypass -File .\Check-CVE-2026-51990.ps1. Requires read access to the filesystem and registry.

noisgate-verify.ps1
POWERSHELLREAD-ONLYSAFE
# Check-CVE-2026-51990.ps1
# Checks whether Sogou Input Method is installed and vulnerable to CVE-2026-51990
# Output: VULNERABLE / PATCHED / UNKNOWN
# Exit codes: 1 = VULNERABLE, 0 = PATCHED, 2 = UNKNOWN

$ErrorActionPreference = 'SilentlyContinue'
$found = $false
$vulnVersion = [version]'16.3.0.3498'

# Check common install paths
$sogouPaths = @(
    "$env:ProgramFiles\SogouInput",
    "${env:ProgramFiles(x86)}\SogouInput",
    "$env:LOCALAPPDATA\SogouInput"
)

foreach ($basePath in $sogouPaths) {
    $bizHelper = Get-ChildItem -Path $basePath -Filter 'biz_helper.exe' -Recurse -ErrorAction SilentlyContinue | Select-Object -First 1
    if ($bizHelper) {
        $found = $true
        $fileVersion = [version]$bizHelper.VersionInfo.FileVersion
        Write-Host "[*] Found Sogou biz_helper.exe at: $($bizHelper.FullName)"
        Write-Host "[*] File version: $fileVersion"
        if ($fileVersion -lt $vulnVersion) {
            Write-Host "[!] VULNERABLE - Version $fileVersion is below patched version $vulnVersion"
            # Also check for sgbiz protocol handler
            $proto = Get-ItemProperty -Path 'Registry::HKEY_CLASSES_ROOT\sgbiz' -ErrorAction SilentlyContinue
            if ($proto) {
                Write-Host "[!] sgbiz: protocol handler is registered - attack surface is active"
            }
            exit 1
        } else {
            Write-Host "[+] PATCHED - Version $fileVersion meets or exceeds $vulnVersion"
            exit 0
        }
    }
}

# Fallback: check registry for sgbiz handler even without finding the binary
$proto = Get-ItemProperty -Path 'Registry::HKEY_CLASSES_ROOT\sgbiz' -ErrorAction SilentlyContinue
if ($proto) {
    Write-Host "[?] sgbiz: protocol handler found but biz_helper.exe not located in standard paths"
    Write-Host "[?] UNKNOWN - manual inspection required"
    exit 2
}

if (-not $found) {
    Write-Host "[+] Sogou Input Method not detected on this host"
    Write-Host "[+] PATCHED (not applicable)"
    exit 0
}