dbcve.org
GlancesApplication · Nicolargo

CVE-2026-30930

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 4.5.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The TimescaleDB export module in Glances builds SQL queries through string concatenation with unsanitized system monitoring data. The normalize() method wraps string values in single quotes but fails to escape embedded single quotes, enabling trivial SQL injection via attacker-controlled process names, filesystem mount points, network interface names, or container names.

MitigationUpgrade to Glances version 4.5.1 or later, which contains the fix for proper escaping of single quotes in the normalize() method.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GlancesApplication
Affected:< 4.5.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Glances version
    Run 'glances --version' or 'pip show glances' to determine the version number
    Affected if Version is lower than 4.5.1
  2. Verify TimescaleDB export is configured
    Look for a configuration file (typically glances.conf or similar) containing 'timescale' or 'tsdb' export settings, or check for the --export-timescale command-line flag in use
    Affected if TimescaleDB export is enabled or configured in the Glances setup
  3. Inspect TimescaleDB export module configuration
    Check the Glances configuration files (usually in /etc/glances/, ~/.config/glances/, or the program's working directory) for export module settings related to TimescaleDB
    Affected if TimescaleDB export is listed among enabled export modules
  4. Confirm database connection settings exist
    Review the Glances TimescaleDB configuration for host, port, database name, and user settings that indicate active export to a TimescaleDB instance
    Affected if TimescaleDB connection parameters are defined and the export module is actively sending data

You are affected if you run Glances version below 4.5.1 with the TimescaleDB export module enabled and configured to send data to a TimescaleDB database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.5.1 or later
Fixed in 4.5.1
Vendor patch github.com →
Interim mitigation

Upgrade to Glances version 4.5.1 or later, which contains the fix for proper escaping of single quotes in the normalize() method.

Recommended fix High confidence

Glances 4.5.1

  1. Check current Glances version with: glances --version
  2. Upgrade Glances to version 4.5.1 or later using pip: pip install --upgrade glances
  3. If using a system package manager (apt, yum, brew, etc.), check for and install the 4.5.1 package or wait for your distribution to sync the update
  4. Verify the upgrade was successful: glances --version
  5. Confirm the installed version is 4.5.1 or higher to ensure the TimescaleDB SQL injection patch is applied
  6. Restart any Glances services or containers running the old version
Caveat Review release notes between your current version and 4.5.1 for any configuration or feature changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Glances Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30930 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-30930 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data