Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-44724 high CVSS 7.8

OS Command Injection in systeminformation (CVE-2026-44724)

Summary

OS command injection in systeminformation (CVE-2026-44724). Successful exploitation can lead to full system takeover. Exploitable via ``systeminformation``. Mitigation: upgrade to `5.31.6` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-44724** has been found in systeminformation. Attackers can target a specific entry point like ``systeminformation`` over the network to misuse the product. Successful exploitation can lead to full system takeover. CVSS score: 7.8/10. What to do: upgrade systeminformation to **5.31.6** or later. If unsure, ask your IT team or search "systeminformation CVE-2026-44724" on the vendor's site.
CVE-2026-44724 (systeminformation) — CWE-78 / CVSS v3 7.8 Attack vector: local / no user interaction Attack surface: `systeminformation` / `connectionName` / `nmcli` / `pwd` Patched: `5.31.6` — apply immediately Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**OS command injection** (CWE-78) exists in systeminformation. Attackers reach the vulnerable code path via ``systeminformation`` without authentication.
📍 Affected scope
systeminformation — . Attack surface: `systeminformation` / `connectionName` / `nmcli` / `pwd`.
🔥 Severity
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **5.31.6**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'systeminformation' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'systeminformation' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `systeminformation` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch 
    Upgrade systeminformation to 5.31.6

    ステージング環境で 5.31.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm systeminformation
[{"type":"SEMVER","events":[{"introduced":"4.17.0"},{"fixed":"5.31.6"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →