Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
3.3
systeminformation library may expose local file contents
published 10 days ago
Summary
The Node.js systeminformation package (versions before 5.33.14) can be tricked into reading any file it can access on the server when a specially crafted network interface name is supplied. This could let a local attacker view sensitive data. Update the package to version 5.33.14 or later to stop the issue.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| Docker Hardened Images:Alpine:3.24 | docker hardened images | supabase-storage | All versions |
| Docker Hardened Images:Debian:13 | docker hardened images | homepage | All versions |
| Docker Hardened Images:Debian:13 | docker hardened images | kibana-9.4 | All versions |
| Docker Hardened Images:Debian:13 | docker hardened images | kibana-9.5 | All versions |
| Docker Hardened Images:Debian:13 | docker hardened images | supabase-storage | All versions |
Original advisory text
systeminformation is a System and OS information library for node.js. Prior to 5.33.14, the Linux networkStats(iface)…
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.
References
- https://scout.docker.com/v/DHI-356y-r5sm-sxgu-u7qv Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-116673 Vendor Advisory
- https://security-tracker.debian.org/tracker/CVE-2026-116673 Vendor Advisory
- https://github.com/advisories/GHSA-4vjg-vx72-qq4g Vendor Advisory
- https://github.com/sebhildebrandt/systeminformation/security/advisories/GHSA-4vj... Vendor Advisory
- https://github.com/sebhildebrandt/systeminformation/commit/8d294b3139fec654a9129... Patch
- https://github.com/sebhildebrandt/systeminformation/releases/tag/v5.33.14 URL
- https://ubuntu.com/security/CVE-2026-116673 Vendor Advisory
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-116673 Vendor Advisory
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit (estimated)
- Gives an attacker partial control (estimated)
Timeline
Published12 Nov 2026
Updated16 Nov 2026
First seen16 Nov 2026
Sources
DHI-356y-r5sm-sxgu-u7qv · OSV
Track software like this
Free during beta