CVE-2026-26318: systeminformation has Command Injection via Unsanitized `locate` Output in `versions()`
systeminformation is a System and OS information library for node.js. Versions prior to 5.31.0 are vulnerable to command injection via unsanitized `locate` output in `versions()`. Version 5.31.0 fixes the issue.
Security readout for executives and security teams
Plain-English summary
A Node.js library used to collect system details can be abused for command injection when its versions() function processes unsanitized locate output. The issue affects systeminformation versions before 5.31.0 and is fixed in 5.31.0. The provided sources do not show active exploitation.
Executive priority
Treat as high priority for systems running affected Node.js services, especially shared or multi-tenant hosts. Patch promptly, but do not assume internet-remote exploitation from the provided evidence because the CVSS vector is local and requires low privileges.
Technical view
CVE-2026-26318 is a CWE-78 command injection flaw in sebhildebrandt systeminformation. The CVSS 3.1 score is 8.8 with local attack vector, low complexity, low privileges required, no user interaction, changed scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Node.js applications or services that include systeminformation before 5.31.0 are potentially exposed, especially where versions() is called. The CVSS vector indicates an attacker needs local low-privileged access, so exposure is highest on shared, multi-user, or already-compromised systems.
Exploitation context
No KEV listing or provided source indicates known active exploitation. The public advisory describes command injection through unsanitized locate output in versions(), but the provided bundle does not include exploit maturity, observed campaigns, or proof-of-concept status.
Researcher notes
Focus on dependency inventory, whether versions() is reachable, and host trust boundaries. Evidence is strong for affected version range and fixed release, but incomplete on exploit availability, downstream distro impact, and real-world exploitation.
Mitigation direction
Upgrade systeminformation to version 5.31.0 or later.
Audit direct and transitive dependencies for systeminformation versions below 5.31.0.
Rebuild and redeploy affected Node.js applications after dependency updates.
Review code paths calling versions() and prioritize those services first.
Track GitHub and Red Hat guidance for downstream package status.
Validation and detection
Confirm production artifacts resolve systeminformation to 5.31.0 or later.
Check package lockfiles and SBOMs for vulnerable versions.
Identify application code paths that call systeminformation versions().
Verify dependency scanners detect CVE-2026-26318 after inventory refresh.
Review the referenced fix commit for expected remediation alignment.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.