CVE-2026-116576: systeminformation vulnerable to Windows command injection in services() through Unicode quotation marks
On Windows, the Node.js package systeminformation builds a PowerShell command from the name passed to `services()`. Its sanitizer keeps Unicode curly quotes, so a crafted name breaks out of the filter string and runs PowerShell with the Node.js process's rights. The report confirms 5.33.15, and the package data marks everything below 5.33.16 as affected. Upgrade to 5.33.16.
Published Oct 28, 2026 · Analysis Oct 31, 2026
What an attacker can do
In lib/processes.js, services() passes each name through sanitizeShellString() and inserts it into a Get-CimInstance Win32_Service -Filter command that util.powerShell() runs. The sanitizer in lib/util.js removes the ASCII double quote but not U+201C or U+201D, the curly double quotes. In its default, non-strict mode it also allows spaces and parentheses. PowerShell treats the curly marks as string delimiters, so an input can close the filter string and add an expression (CWE-78).
The reporter's proof of concept passes a name that ends the string and calls New-Item. On Windows it created a marker file as the Node.js process account. The attacker needs the application to pass attacker-controlled text into services(). The reporter found no network route in the package itself. A test HTTP server they wrote did trigger it through a query parameter, so exposure depends on the application that uses the package. getDynamicData() also reaches services().
Code runs as the Node.js process account. Depending on that account, it can read or change files, alter application data or disrupt the service. The CVSS 3.1 vector is local with low privileges, score 7.8. Linux and macOS are not part of the report. The project's own docs/security.html already warns about untrusted input to services().
Who is affected
The npm package systeminformation below 5.33.16 on Windows. The report confirms 5.33.15 only and says other versions were not checked, while the package data lists everything below 5.33.16. You are exposed only if your code passes untrusted text to services() or getDynamicData(). Check:
npm ls systeminformationSearch your code for calls to si.services( and see where the argument comes from.
systeminformation
- Ecosystem
- npm
- Affected
- < 5.33.16
- Fixed in
- 5.33.16
- Check
npm ls systeminformation
How to fix it
Upgrade to systeminformation 5.33.16, the patched version (commit 5014c6d):
npm install [email protected]The sanitizer now also strips Unicode quotes and dashes, and Windows service names are checked against a whitelist of allowed characters. The advisory gives no other workaround. Until you upgrade, do not pass user input to services(), or validate it against a strict list of known service names first.
How to tell if you were hit
Look for PowerShell processes spawned by your Node.js process whose command line holds Get-CimInstance Win32_Service -Filter followed by extra expressions such as New-Item or Invoke-WebRequest. Check application logs and request logs for service-name parameters containing U+201C or U+201D, or unusual parentheses. Also look for unexpected files created by the Node.js service account.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Summary
On Windows, [email protected] builds a PowerShell command using the value passed to services(). The default sanitizer removes ASCII quotes but keeps Unicode curly quotes, spaces, and parentheses. A crafted service name can use those characters to break out of the generated filter string and run a PowerShell expression. The expression runs with the permissions of the Node.js process.
This report confirms version 5.33.15. Other package versions have not been checked.
Details
In lib/processes.js, services() sanitizes the caller's string with sanitizeShellString() and later inserts each resulting name into a Get-CimInstance Win32_Service -Filter command. The Windows branch passes that command to util.powerShell().
The sanitizer in lib/util.js removes the ASCII double quote, but it does not remove U+201C or U+201D, the left and right curly double quotation marks. It also permits spaces and parentheses when called in its default, non-strict mode. PowerShell accepts the curly marks as string delimiters, so an input can end the filter string and place a command expression in the generated command.
For example, the input below uses curly quotation marks to end the generated filter string and execute New-Item. I reproduced this call on Windows against the checked-out [email protected] source; it created a marker file with the Node.js process account.
Proof of concept
Run this on Windows in a disposable directory with Node.js and PowerShell available:
mkdir si-command-injection-repro
cd si-command-injection-repro
npm init -y
npm install [email protected]Save the following as poc.cjs, then run node poc.cjs:
'use strict';
const fs = require('node:fs');
const path = require('node:path');
const si = require('systeminformation');
(async () => {
const markerName = `si-injection-${process.pid}.txt`;
const markerPath = path.join(process.cwd(), markerName);
fs.rmSync(markerPath, { force: true });
try {
await si.services(`not-a-service” (New-Item -Name ${markerName} -ItemType File -Force) “`);
console.log(`markerCreated=${fs.existsSync(markerPath)}`);
} finally {
fs.rmSync(markerPath, { force: true });
}
})().catch((error) => {
console.error(error);
process.exitCode = 1;
});Expected output:
markerCreated=trueThe Windows run returned an array and created the marker (markerCreated: true). A benign input left the marker absent. The script removes the marker afterward. I did not identify an application network route that forwards remote input to services(), so remote exploitability depends on the consuming application.
Impact
An application that passes attacker-controlled input to services() on Windows can execute PowerShell commands with the Node.js process account's permissions. Depending on that account, commands may read or change accessible files, alter application data, or disrupt the service. I searched this repository for HTTP servers, route handlers, and listener calls and found none. services() is exposed through the package API and getDynamicData(), so a consuming application could make the input network-reachable if it forwards request data. A separate loopback HTTP harness did trigger the command through a query parameter, but that server was test code and is not part of this repository. The project's docs/security.html already warns that arbitrary untrusted input to services() needs caution because package sanitization does not cover every case.
Credited to itsFM-Codes.
Questions
- Can this be exploited remotely?
Only through the application that uses the package. The reporter found no network route in systeminformation itself, but an app that forwards request data to
services()makes it reachable.- Does it affect Linux or macOS?
The advisory describes the Windows PowerShell path only. It does not report an issue on other platforms.
- Which version fixes CVE-2026-116576?
5.33.16. The report confirmed the bug in 5.33.15 and did not check other versions.
- What do the curly quotes do?
PowerShell accepts U+201C and U+201D as string delimiters, but the old sanitizer only removed ASCII quotes, so they closed the generated filter string.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-116673
systeminformation has path traversal in Linux networkStats() that allows symlink-based file disclosure outside /sys/class/net
low3.3Oct 28, 2026CVE-2026-116674
systeminformation has prototype pollution in `networkStats()` via the interface name
medium6.5Oct 28, 2026CVE-2026-50289
systeminformation: OS command injection in networkInterfaces() via interfaces(5) source-directive path on Linux
high8.7Jul 15, 2026CVE-2026-44724
Systeminformation vulnerable to Linux command injection in networkInterfaces() via unsanitized NetworkManager connection profile name
high7.8May 13, 2026CVE-2026-26280
Systeminformation has a Command Injection via unsanitized interface parameter in wifi.js retry path
high8.4Feb 18, 2026CVE-2026-26318
Command Injection via Unsanitized `locate` Output in `versions()` — systeminformation
high8.8Feb 18, 2026
