Homepage

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') Affecting node-systeminformation package, versions *

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.29% (22nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIANUNSTABLE-NODESYSTEMINFORMATION-21771266
  • published28 Oct 2026
  • disclosed27 Oct 2026
Report a new vulnerability Found a mistake?

Introduced: 27 Oct 2026

NewCVE-2026-116674  (opens in a new tab)
CWE-1321  (opens in a new tab)

How to fix?

There is no fixed version for Debian:unstable node-systeminformation.

NVD Description

Note: Versions mentioned in the description apply only to the upstream node-systeminformation package and not the node-systeminformation package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

systeminformation is a System and OS information library for node.js. Prior to 5.33.13, networkStats(ifaces) in lib/network.js on FreeBSD, OpenBSD, and NetBSD stores per-interface data in the plain-object _network cache and indexes it with the sanitized caller-controlled interface name. Passing proto causes the inherited Object.prototype value to be used instead of creating an own cache entry, so calcNetworkSpeed() writes rx_bytes, tx_bytes, rx_sec, tx_sec, ms, last_ms, and operstate onto Object.prototype. The polluted property names are fixed and their values come from interface statistics, but inherited-name collisions and enumerable keys can corrupt application branching, serialization, configuration merging, validation, or lookup behavior. This issue is fixed in version 5.33.13.