# CVE-2026-26318: systeminformation has Command Injection via Unsanitized `locate` Output in `versions()`

> Attackers can execute arbitrary commands via unsanitized locate output in the versions function of the systeminformation library.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Feb 2026
- **Updated:** 15 Jul 2026
- **Also known as:** CLEANSTART-2026-QA36813, DEBIAN-CVE-2026-26318, ECHO-4230-283f-f661, GHSA-5vv4-hvf7-2h46, MINI-2w4h-776p-34g7, MINI-4qxw-rrcv-8j29, MINI-5786-3wq8-54fj, MINI-8hvr-rjq4-5qr5, MINI-cvmc-4254-47f5, MINI-g6r2-2827-gwpw, MINI-h7gq-hcx5-4cp4, MINI-mhf9-gg69-885h, MINI-mp54-xwgv-g593, ROOT-APP-NPM-CVE-2026-26318, UBUNTU-CVE-2026-26318

## What is CVE-2026-26318?

CVE-2026-26318 is a high-severity command injection vulnerability in sebhildebrandt systeminformation, published on 19 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-26318?

2 open source packages ship an affected version, including systeminformation. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `systeminformation` | npm | All versions | 5.31.0 |
| `systeminformation` | npm | All versions | 5.31.0 |

Products: Systeminformation Systeminformation.

## How do I fix CVE-2026-26318?

Upgrade systeminformation to 5.31.0 or later.

## Is CVE-2026-26318 being exploited?

There is no known exploitation of CVE-2026-26318 in the wild and no public exploit code.

## Other vulnerabilities in sebhildebrandt systeminformation

- [CVE-2023-42810](https://insights.sbomify.com/CVE-2023-42810/): systeminformation SSID Command Injection Vulnerability (critical 9.8)
- [CVE-2021-21388](https://insights.sbomify.com/CVE-2021-21388/): Command Injection Vulnerability in systeminformation (high 8.9)
- [CVE-2020-7752](https://insights.sbomify.com/CVE-2020-7752/): Command Injection (high 8.8)
- [CVE-2026-50289](https://insights.sbomify.com/CVE-2026-50289/): systeminformation: OS command injection in networkInterfaces() via interfaces(5) source-directive path on Linux (high 8.7)
- [CVE-2026-26280](https://insights.sbomify.com/CVE-2026-26280/): Systeminformation has a Command Injection via unsanitized interface parameter in wifi.js retry path (high 8.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26318 and fix it if it is affected.

What it is: CVE-2026-26318 is a high-severity command injection vulnerability in sebhildebrandt systeminformation, published on 19 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-26318 in the wild and no public exploit code.

Affected packages and fixed versions:
- systeminformation (npm): affected all versions; fixed in 5.31.0
- systeminformation (npm): affected all versions; fixed in 5.31.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26318/ (Markdown: https://insights.sbomify.com/CVE-2026-26318/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26318
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26318
- OSV: https://osv.dev/vulnerability/CVE-2026-26318

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26318/
Summaries are generated and may contain mistakes; the official description above is the record.