Quick answers
- Is CVE-2026-116674 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116674 being exploited in the wild.
- How severe is CVE-2026-116674?
- Medium severity, with a CVSS score of 6.5, published 27 October 2026.
- Which products and versions are affected?
- systeminformation (npm) < 5.33.13, SEMVER:introduced=0,fixed=5.33.13; Sebhildebrandt Systeminformation before 5.33.13.
- Is there a fix for CVE-2026-116674?
- Yes. systeminformation (npm): upgrade to 5.33.13 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116674 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-116674?
- Check whether you run systeminformation (npm) or Sebhildebrandt Systeminformation at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- systeminformation (npm): upgrade to 5.33.13 or later
npm install systeminformation@5.33.13
Technical details
The networkStats(ifaces) function in lib/network.js on FreeBSD, OpenBSD, and NetBSD uses unsanitized caller-controlled interface names as object keys in a plain-object cache, allowing an attacker to index with "__proto__" to pollute Object.prototype. The function then writes interface statistics (rx_bytes, tx_bytes, rx_sec, tx_sec, ms, last_ms, operstate) to this polluted prototype, affecting property enumeration and inheritance across the application.
Affected products
- sebhildebrandt systeminformation before 5.33.13
Identifiers
- CVE-2026-116674
- GHSA-7648-jmwf-vw7j
Timeline
- 2026-10-27: disclosed
- 2026-09-20: patched