# CVE-2026-120275 — Shanghai Xi Yu Ji Zhi Technology Minimax Code

> As of 2026-11-02, CVE-2026-120275 is a MEDIUM-severity vulnerability in Shanghai Xi Yu Ji Zhi Technology Minimax Code, CVSS v3.1 5.5. No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-120275 as of 2026-11-02; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-11-02

## What is CVE-2026-120275?

A security flaw has been discovered in Shanghai Xi Yu Ji Zhi Technology Minimax Code 0.5.8. This affects an unknown part of the component Find Command Handler. The manipulation of the argument -exec results in os command injection. The attack may be performed from remote. The vendor was contacted early about this disclosure but did not respond in any way.

The record classifies CVE-2026-120275 under weakness classes [CWE-78](https://intel.threadlinqs.com/cwe/CWE-78), [CWE-77](https://intel.threadlinqs.com/cwe/CWE-77). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs a user to take an action first. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 18 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 5.5 — MEDIUM (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L/E:X/RL:X/RC:C`)
- **CVSS v4.0 base score:** 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 2.8/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-11-01

## Is CVE-2026-120275 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **Shanghai Xi Yu Ji Zhi Technology**: Minimax Code

## How to fix CVE-2026-120275

No vendor patch reference has been recorded for CVE-2026-120275 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-120275

No threat campaign in the Threadlinqs corpus currently references CVE-2026-120275, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, GitHub Security Advisories.

**Technical analysis**

- [vuldb.com — vdb entry](https://vuldb.com/vuln/429619)

**Third-party advisory**

- [vuldb.com — signature](https://vuldb.com/vuln/429619/cti)
- [vuldb.com — third party advisory](https://vuldb.com/cve/CVE-2026-120275)
- [vuldb.com — third party advisory (1007426)](https://vuldb.com/submit/1007426)

**Other references**

- [mcniyfj5bw9b.feishu.cn — related](https://mcniyfj5bw9b.feishu.cn/docx/RenxdtY52oBlqRxN4S7csZtNnUc)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-120275
No Threadlinqs detection currently covers CVE-2026-120275; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
