ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-116674

systeminformation has prototype pollution in via the interface name

Published Oct 28, 2026 · catalog updated Oct 28, 2026 · systeminformation has prototype pollution

Last checked Nov 4, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-116674. EPSS is 0.29%. Act only if a listed version of systeminformation has prototype pollution is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (systeminformation has prototype pollution).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium6.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.29%
Remediation
Version ranges on file
Affected products
npm systeminformation

## Summary keeps a per interface cache for computing / between calls. The cache is a plain JavaScript object and is indexed with the interface name the caller supplied. Passing the name makes every cache write land on instead of the cache, polluting every object in the Node.js process. An application is affected if it passes untrusted input as the argument of and runs on FreeBSD, OpenBSD or NetBSD. ## Details ### The vulnerable code declares the cache as a plain object: writes into it, keyed by the interface name: With this misbehaves twice: 1. does not read a missing own property — it invokes the inherited getter and returns , which is truthy. The guard therefore never creates the placeholder. 2. Each following assignment writes onto . After one call, , , , , , and are visible on **every** object in the process. A second call takes the other branch ( is now truthy) and keeps them updated. ### Why the existing sanitizing does not help The interface name does pass through before it is used as the cache key. That function is a **shell metacharacter** filter, built to stop command injection in the / invocations — a different threat. Property names made of letters and underscores are legitimate interface names and pass through untouched: The sanitizer is doing its job; the gap is that no layer treats the value as an *object key*. ### Reachability The cache write is guarded incidentally on three of four platform branches. These guards exist for unrelated reasons and are not a deliberate defence: | Platform | Code path | Reachable with an arbitrary name? | | --- | --- | --- | | Linux / Android | | **No** — a non-existent interface returns early | | macOS | requires to emit a data row beyond the header | **No** — verified on macOS 27, stays clean | | Windows | — requires a real adapter match | **No** | | **FreeBSD / OpenBSD / NetBSD** | | **Yes** — the call sits outside the parsing loop, so any successful exit reaches it, and prints only its header and exits | The importan

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm systeminformation< 5.33.13

How to fix CVE-2026-116674

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-116674. EPSS is 0.29%. Act only if a listed version of systeminformation has prototype pollution is installed.

Which versions are affected?

Compare what you have installed with < 5.33.13. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-1321: Improperly Controlled Modification of Object Prototype Attributes (Prototype Pollution). EPSS 0.29%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 28, 2026 · GitHub Advisory Database

    Detected

    ## Summary keeps a per interface cache for computing / between calls. The cache is a plain JavaScript object and is indexed with the interface name the caller supplied. Passing the name makes every cache write land on instead of the cache, polluting every object in the Node.js process. An application is affected if it passes untrusted input as the argument of and runs on FreeBSD, OpenBSD or NetBSD

  2. Oct 28, 2026 · GitHub Advisory Database

    Updated

    ## Summary keeps a per interface cache for computing / between calls. The cache is a plain JavaScript object and is indexed with the interface name the caller supplied. Passing the name makes every cache write land on instead of the cache, polluting every object in the Node.js process. An application is affected if it passes untrusted input as the argument of and runs on FreeBSD, OpenBSD or NetBSD

Sources

  • CVE.orgVulnerability recordCVE-2026-116674

    Official CVE identifier

    cve.org
  • GitHub Advisory DatabasePackage advisoryGHSA-7648-jmwf-vw7j

    systeminformation has prototype pollution in via the interface name

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-116674

    networkStats() keeps a per interface cache for computing rx_sec / tx_sec between calls. The cache is a plain JavaScript object and is indexed with the interface name the caller supplied. Passing the name proto makes every cache write land on Object.prototype instead of the cache, polluting every object in the Node.js process. An application is affected if it passes untrusted input as the ifaces ar

    advisories.gitlab.com

References

Freshness

Last verified in this catalog Nov 4, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • CVE.orgOct 29, 2026
  • GitLab Advisory DatabaseOct 29, 2026
  • GitHub Advisory DatabaseOct 29, 2026