# CVE-2026-120422: Insecure HTTP configuration retrieval in Sogou Input Method allows arbitrary code execution


- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:H/S:N/R:U/V:D/RE:M`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-8j99-xfj8-8r32

## What is CVE-2026-120422?

CVE-2026-120422 is a high-severity vulnerability in Sogou Input Method, published on 4 Nov 2026. 

### Official description

Sogou Input Method for Windows contains a vulnerability in the configuration retrieval mechanism of its SGTool.exe component. The application retrieves configuration data over unencrypted HTTP connections, allowing an attacker capable of manipulating network traffic to replace legitimate server responses with malicious configurations. An attacker can exploit this vulnerability to instruct SGTool.exe to download attacker-controlled files to arbitrary locations, including paths used by legitimate application components. This can result in arbitrary code execution when the downloaded files are subsequently executed or loaded by the application.

Weakness: CWE-1428 (Reliance on HTTP instead of HTTPS)

## Which versions are affected by CVE-2026-120422?


## How do I fix CVE-2026-120422?

No fix has been published for CVE-2026-120422 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120422 being exploited?

There is no known exploitation of CVE-2026-120422 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120422 and fix it if it is affected.

What it is: CVE-2026-120422 is a high-severity vulnerability in Sogou Input Method, published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120422 in the wild and no public exploit code.

Affected product: Sogou Input Method. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120422/ (Markdown: https://insights.sbomify.com/CVE-2026-120422/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120422
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120422
- OSV: https://osv.dev/vulnerability/CVE-2026-120422

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120422/
Summaries are generated and may contain mistakes; the official description above is the record.
