dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-44724

HIGH · 7.8 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
systeminformation is a System and OS information library for node.js. From 4.17.0 to 5.31.5, on Linux, systeminformation is vulnerable to command injection in networkInterfaces() when an active NetworkManager connection profile name contains shell metacharacters. The vulnerable value is obtained internally from real nmcli device status output. The library sanitizes the network interface name before using it in shell commands, but it does not apply equivalent sanitization to the parsed NetworkManager connection profile name. That unsanitized connectionName is then interpolated into three shell command strings executed through execSync(). This vulnerability is fixed in 5.31.6.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The systeminformation Node.js library versions 4.17.0 to 5.31.5 on Linux contain a command injection vulnerability in the networkInterfaces() function. The library sanitizes network interface names before using them in execSync() shell commands but fails to sanitize NetworkManager connection profile names, allowing shell metacharacters in connection names to execute arbitrary commands.

MitigationUpgrade systeminformation to version 5.31.6 or later to patch the command injection vulnerability in networkInterfaces().

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify systeminformation library version
    Run 'npm list systeminformation' or check package.json dependencies to find the installed version of the systeminformation package
    Affected if The installed version is between 4.17.0 and 5.31.5 inclusive
  2. Confirm Linux environment
    Check that the host OS is Linux (uname -a or cat /etc/os-release)
    Affected if The system is running Linux; this vulnerability only affects Linux systems
  3. Verify NetworkManager is in use
    Check if NetworkManager is active: run 'systemctl status NetworkManager' or check for nmcli availability with 'which nmcli'
    Affected if NetworkManager is installed and active; the vulnerable code path executes nmcli commands
  4. Inspect NetworkManager connection profile names
    List all NetworkManager connection profiles with 'nmcli connection show' and examine the NAME column for shell metacharacters such as $`, $(, ;, |, &, >, <, *, ?, or spaces
    Affected if Any connection profile name contains shell metacharacters ($, ;, |, &, (, ), >, <, *, ?, or backticks) that could be interpreted as command injection
  5. Confirm application uses networkInterfaces function
    Search application code for calls to si.networkInterfaces() or systeminformation networkInterfaces function
    Affected if The application code invokes the networkInterfaces() function from systeminformation, which triggers the vulnerable execSync call

A user is affected if they have systeminformation version 4.17.0-5.31.5 installed on Linux with NetworkManager active, and their application calls networkInterfaces() while any NetworkManager connection profile name contains shell metacharacters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade systeminformation to version 5.31.6 or later to patch the command injection vulnerability in networkInterfaces().

Recommended fix High confidence

systeminformation version 5.31.6 or later

  1. 1. Identify all projects and applications that depend on the 'systeminformation' npm package
  2. 2. Run 'npm list systeminformation' or 'npm ls systeminformation' in each project to check the current installed version
  3. 3. If the installed version is between 4.17.0 and 5.31.5 inclusive, upgrade by running: npm install [email protected] (or newer stable version)
  4. 4. Update package.json to pin the fixed version: npm install systeminformation@^5.31.6
  5. 5. Run npm install to update the lockfile
  6. 6. Rebuild and redeploy applications to ensure the patched library is used
  7. 7. Test the networkInterfaces() function to confirm it works correctly with NetworkManager connection profiles containing special characters
  8. 8. Audit other dependencies for any potential command injection vulnerabilities
Caveat None documented for this security patch; this is a bug fix release addressing a security vulnerability

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44724 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44724 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data