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.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 20260929
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Security Toolbox
fixed in 20260929
References 1
GitHub · mandiant/Vulnerability-Disclosures
Questions about CVE-2026-105044
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: github.com
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: github.com
What should I do about it?
Update the Security Toolbox rule package to version 20260929 or later. The advisory lists no workaround.Source: github.com
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: cve.now feed data