# CVE-2026-30930: Glances has SQL Injection via Process Names in TimescaleDB Export

> Attackers can inject SQL commands via process names in Glances' TimescaleDB export, potentially reading or modifying database contents.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Mar 2026
- **Updated:** 11 Mar 2026
- **Also known as:** DEBIAN-CVE-2026-30930, GHSA-x46r-mf5g-xpr6, PYSEC-2026-2165, UBUNTU-CVE-2026-30930

## What is CVE-2026-30930?

CVE-2026-30930 is a high-severity SQL injection vulnerability in nicolargo glances, published on 10 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Glances is an open-source system cross-platform monitoring tool. Prior to 4.5.1, The TimescaleDB export module constructs SQL queries using string concatenation with unsanitized system monitoring data. The normalize() method wraps string values in single quotes but does not escape embedded single quotes, making SQL injection trivial via attacker-controlled data such as process names, filesystem mount points, network interface names, or container names. This vulnerability is fixed in 4.5.1.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

3 open source packages ship an affected version, including glances and Glances. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `glances` | PyPI | All versions | 4.5.1 |
| `glances` | PyPI | All versions | 4.5.1 |
| `Glances` | PyPI | All versions | 4.5.1 |

Products: Nicolargo Glances.

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

Upgrade glances to 4.5.1 or later.

## Is CVE-2026-30930 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30930 exists.

## Other vulnerabilities in nicolargo glances

- [CVE-2026-32633](https://insights.sbomify.com/CVE-2026-32633/): Glances's Browser API Exposes Reusable Downstream Credentials via `/api/4/serverslist` (critical 9.1)
- [CVE-2026-32596](https://insights.sbomify.com/CVE-2026-32596/): Glances exposes the REST API without authentication (high 8.7)
- [CVE-2026-30928](https://insights.sbomify.com/CVE-2026-30928/): Glances Exposes Unauthenticated Configuration Secrets (high 8.7)
- [CVE-2026-32610](https://insights.sbomify.com/CVE-2026-32610/): Glances's Default CORS Configuration Allows Cross-Origin Credential Theft (high 8.1)
- [CVE-2026-32634](https://insights.sbomify.com/CVE-2026-32634/): Glances Central Browser Autodiscovery Leaks Reusable Credentials to Zeroconf-Spoofed Servers (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-30930 is a high-severity SQL injection vulnerability in nicolargo glances, published on 10 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30930 exists.

Affected packages and fixed versions:
- glances (PyPI): affected all versions; fixed in 4.5.1
- glances (PyPI): affected all versions; fixed in 4.5.1
- Glances (PyPI): affected all versions; fixed in 4.5.1

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-30930/ (Markdown: https://insights.sbomify.com/CVE-2026-30930/index.md)
```

## Sources

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

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