Glances has SQL Injection via Process Names in TimescaleDB Export
CVE-2026-30930GHSA-x46r-mf5g-xpr6
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (glances 4.5.1), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI glances
- Affected
- < 4.5.1
- Fixed in
- 4.5.1
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-x46r-mf5g-xpr6 lists affected ranges: PyPI glances >=0 <4.5.1 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-x46r-mf5g-xpr6 lists affected ranges: PyPI glances >=0 <4.5.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 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 · score source
- EPSS
- CVE-2026-30930: 0.38% estimated exploitation activity in the next 30 days; percentile 31.86 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary 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. Root Cause: The normalize() function uses f"'{value}'" for string values without escaping single quotes within the value. The resulting strings are concatenated into INSERT queries via string formatting and executed directly with cur.execute() — no parameterized queries are used. Affected Code - File: glances/exports/glancestimescaledb/init.py, lines 79-93 (normalize function) - File: glances/exports/glancestimescaledb/init.py, lines 201-205 (query construction) PoC - As a normal user, create a process with the name containing the SQL Injection payload: - Start Glances with TimescaleDB export as root user:…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-x46r-mf5g-xpr6
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-x46r-mf5g-xpr6
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-30930 Advisory: Glances has SQL Injection via Process Names in TimescaleDB Export IDs: CVE-2026-30930, GHSA-x46r-mf5g-xpr6 Record: https://patchnext.com/advisories/cve-2026-30930 (revision 3, source checked 26 Oct 2026, 13:37 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: glances 4.5.1. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI glances: affected < 4.5.1; fixed in 4.5.1 ## Suggested inspection (read-only) - `python -m pip show glances`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on glances. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-x46r-mf5g-xpr6 (OSV record GHSA-x46r-mf5g-xpr6 lists affected ranges: PyPI glances >=0 <4.5.1 (fixed)) - Verified: https://github.com/advisories/GHSA-x46r-mf5g-xpr6 (GitHub-reviewed advisory GHSA-x46r-mf5g-xpr6 lists affected ranges: PyPI glances >=0 <4.5.1) Commands are suggestions: review each one before running it.
Loading voting…