Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Glances versions before 4.5.2 have a SQL injection flaw in the DuckDB export module, where table and column names taken from monitoring statistics are interpolated directly into DDL and INSERT statements without quoting or parameterization. The source says exploitation requires a plugin or stat key that carries attacker-controlled names, which it describes as a future risk rather than a current one, and it gives few details on a concrete path. A successful injection could corrupt the DuckDB database or create unauthorized tables. Upgrade to Glances 4.5.2 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.0 | High | 3.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0037, the 30th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:04 UTC First seen by agentprime
- 31 Oct 2026, 15:04 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-49g7-2ww7-3vf5
- OSV: GHSA-49g7-2ww7-3vf5
- github.com/nicolargo/glances/security/advisories/GHSA-49g7-2ww7-3vf5
- nvd.nist.gov/vuln/detail/CVE-2026-32611
- github.com/nicolargo/glances/commit/63b7da28895249d775202d639e5531ba63491a5c
- github.com/nicolargo/glances
- github.com/nicolargo/glances/releases/tag/v4.5.2