VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

glances: vulnerability history, versions and safety

glances is a package in the PyPI ecosystem. Vulert records 52 vulnerabilities for it across 120 releases, from Jul 2021 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
52 vulnerabilities recorded C1 H19 M6 U26
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
50 in the last 12 months

Most recent disclosure 19 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all glances vulnerabilities

Vulert verdict on glances 4.5.8 i

Updated on 23 Oct 2026

Careful: 4.5.8 has 3 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 4.5.8 — affected i
  • Vulnerabilities on record 52 over 5 years · 50 in the last year i
  • Latest disclosure 19 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 2 i
  • Depended on by 4 packages i
  • Stars 33,819 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence LGPL-3.0-only i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for glances, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.5.8 11 Oct 2026 H2 U1 LGPL-3.0-only No Details →
4.5.8.dev1 11 Oct 2026 H2 U1 LGPL-3.0-only No Details →
4.5.7 26 Sep 2026 H2 U1 LGPL-3.0-only No Details →
4.5.6 01 Aug 2026 H2 U1 LGPL-3.0-only No Details →
4.5.5 13 Jun 2026 H3 M2 U5 LGPL-3.0-only Yes Details →
4.5.4 19 Apr 2026 H7 M3 U10 LGPL-3.0-only Yes Details →
4.5.3 31 Mar 2026 H9 M4 U13 LGPL-3.0-only Yes Details →
4.5.2 14 Mar 2026 H10 M4 U15 LGPL-3.0-only No Details →
4.5.1 07 Mar 2026 C1 H16 M5 U22 LGPL-3.0-only No Details →
4.5.0.5 17 Feb 2026 C1 H18 M5 U24 LGPL-3.0-only No Details →
4.5.0.4 10 Feb 2026 C1 H18 M5 U24 LGPL-3.0-only No Details →
4.5.0.3 10 Feb 2026 C1 H18 M5 U24 LGPL-3.0-only No Details →
4.5.0.2 10 Feb 2026 C1 H18 M5 U24 LGPL-3.0-only No Details →
4.5.0.1 08 Feb 2026 C1 H18 M5 U24 LGPL-3.0-only No Details →
4.5.0 08 Feb 2026 C1 H18 M5 U24 LGPL-3.0-only No Details →
4.4.1 03 Nov 2025 C1 H18 M5 U24 LGPL-3.0 No Details →
4.4.0 02 Nov 2025 C1 H18 M5 U24 LGPL-3.0 No Details →
4.3.3 09 Jul 2025 C1 H18 M5 U24 LGPL-3.0 No Details →
4.3.2 05 Jul 2025 C1 H18 M5 U24 LGPL-3.0 No Details →
4.3.1 22 Mar 2025 C1 H18 M5 U24 LGPL-3.0 No Details →
4.3.0.8 04 Jan 2025 C1 H18 M5 U24 LGPL-3.0 No Details →
4.3.0.7 03 Jan 2025 C1 H18 M5 U24 LGPL-3.0 No Details →
4.3.0.6 30 Dec 2024 C1 H18 M5 U24 LGPL-3.0 No Details →
4.3.0.5 28 Dec 2024 C1 H18 M5 U24 LGPL-3.0 No Details →
4.3.0.4 28 Dec 2024 C1 H18 M5 U24 LGPL-3.0 No Details →
4.3.0.3 27 Dec 2024 C1 H18 M5 U24 LGPL-3.0 No Details →
4.3.0.1 27 Dec 2024 C1 H18 M5 U24 LGPL-3.0 No Details →
4.3.0 27 Dec 2024 C1 H18 M5 U24 LGPL-3.0 No Details →
4.2.1 01 Nov 2024 C1 H18 M5 U24 LGPL-3.0 No Details →
4.2.0 20 Oct 2024 C1 H18 M5 U24 LGPL-3.0 No Details →
4.1.2 03 Jul 2024 C1 H18 M5 U24 LGPL-3.0 No Details →
4.1.1 29 Jun 2024 C1 H18 M5 U24 LGPL-3.0 No Details →
4.1.0 29 Jun 2024 C1 H18 M5 U24 LGPL-3.0 No Details →
4.0.8 08 Jun 2024 C1 H18 M5 U24 LGPL-3.0 No Details →
4.0.7 25 May 2024 C1 H17 M5 U23 LGPL-3.0 No Details →
4.0.6 25 May 2024 C1 H17 M5 U23 LGPL-3.0 No Details →
4.0.5 18 May 2024 C1 H17 M5 U23 LGPL-3.0 No Details →
4.0.4 15 May 2024 C1 H17 M5 U23 LGPL-3.0 No Details →
4.0.3 15 May 2024 C1 H17 M5 U23 LGPL-3.0 No Details →
4.0.2 13 May 2024 C1 H17 M5 U23 LGPL-3.0 No Details →
4.0.1 12 May 2024 C1 H17 M5 U23 LGPL-3.0 No Details →
3.4.0.5 23 Mar 2024 C1 H17 M5 U23 LGPL-3.0 No Details →
3.4.0.4 23 Mar 2024 C1 H17 M5 U23 LGPL-3.0 No Details →
3.4.0.3 20 May 2023 C1 H17 M5 U23 LGPL-3.0 No Details →
3.4.0.2 18 May 2023 C1 H17 M5 U23 LGPL-3.0 No Details →
3.4.0.1 17 May 2023 C1 H17 M5 U23 LGPL-3.0 No Details →
3.4.0 16 May 2023 C1 H17 M5 U23 LGPL-3.0 No Details →
3.3.1.1 17 Jan 2023 C1 H17 M5 U23 LGPL-3.0 No Details →
3.3.1 14 Jan 2023 C1 H17 M5 U23 LGPL-3.0 No Details →
3.3.0.4 03 Nov 2022 C1 H17 M5 U23 LGPL-3.0 No Details →
3.3.0.3 03 Nov 2022 C1 H17 M5 U23 LGPL-3.0 No Details →
3.3.0.2 30 Oct 2022 C1 H17 M5 U23 LGPL-3.0 No Details →
3.3.0.1 17 Oct 2022 C1 H17 M5 U23 LGPL-3.0 No Details →
3.3.0 16 Oct 2022 C1 H17 M5 U23 LGPL-3.0 No Details →
3.2.7 28 Jul 2022 C1 H17 M5 U23 LGPL-3.0 No Details →
3.2.6.4 26 May 2022 C1 H17 M5 U23 LGPL-3.0 No Details →
3.2.6.3 25 May 2022 C1 H17 M5 U23 LGPL-3.0 No Details →
3.2.6.2 25 May 2022 C1 H17 M5 U23 LGPL-3.0 No Details →
3.2.6.1 24 May 2022 C1 H17 M5 U23 LGPL-3.0 No Details →
3.2.5 10 Apr 2022 C1 H17 M5 U23 LGPL-3.0 No Details →
3.2.4.2 22 Nov 2021 C1 H17 M5 U23 LGPL-3.0 No Details →
3.2.4.1 21 Nov 2021 C1 H17 M5 U23 LGPL-3.0 No Details →
3.2.4 20 Nov 2021 C1 H17 M5 U23 LGPL-3.0 No Details →
3.2.3.1 21 Aug 2021 C1 H17 M5 U23 LGPL-3.0 No Details →
3.2.3 14 Aug 2021 C1 H17 M5 U23 LGPL-3.0 No Details →
3.2.2 24 Jul 2021 C1 H17 M5 U23 LGPL-3.0 No Details →
3.2.1 10 Jul 2021 C1 H17 M5 U23 LGPL-3.0 No Details →
3.2.0 03 Jul 2021 C1 H17 M6 U24 LGPL-3.0 No Details →
3.1.7 02 May 2021 C1 H17 M6 U24 LGPL-3.0 No Details →
3.1.6.2 07 Feb 2021 C1 H17 M6 U24 LGPL-3.0 No Details →
3.1.6.1 24 Jan 2021 C1 H17 M6 U24 LGPL-3.0 No Details →
3.1.6 23 Jan 2021 C1 H17 M6 U24 LGPL-3.0 No Details →
3.1.5 19 Aug 2020 C1 H17 M6 U24 LGPL-3.0 No Details →
3.1.4.1 25 Mar 2020 C1 H17 M6 U24 LGPL-3.0 No Details →
3.1.4 10 Mar 2020 C1 H17 M6 U24 LGPL-3.0 No Details →
3.1.3 13 Oct 2019 C1 H17 M6 U24 LGPL-3.0 No Details →
3.1.2 27 Aug 2019 C1 H17 M6 U24 LGPL-3.0 No Details →
3.1.1 17 Jul 2019 C1 H17 M6 U24 LGPL-3.0 No Details →
3.1.0 19 Jan 2019 C1 H17 M6 U24 LGPL-3.0 No Details →
3.0.2 29 Sep 2018 C1 H17 M6 U24 LGPL-3.0 No Details →
3.0.1 04 Sep 2018 C1 H17 M6 U24 LGPL-3.0 No Details →
3.0.0 01 Sep 2018 C1 H17 M6 U24 LGPL-3.0 No Details →
2.11.1 09 Sep 2017 C1 H17 M6 U24 LGPL-3.0 No Details →
2.11.0 27 Aug 2017 C1 H17 M6 U24 LGPL-3.0 No Details →
2.10.0 26 May 2017 C1 H17 M6 U24 LGPL-3.0 No Details →
2.9.1 29 Mar 2017 C1 H17 M6 U24 LGPL-3.0 No Details →
2.9.0 27 Mar 2017 C1 H17 M6 U24 LGPL-3.0 No Details →
2.8.8 12 Mar 2017 C1 H17 M6 U24 LGPL-3.0 No Details →
2.8.7 12 Mar 2017 C1 H17 M6 U24 LGPL-3.0 No Details →
2.8.6 11 Mar 2017 C1 H17 M6 U24 LGPL-3.0 No Details →
2.8.5 10 Mar 2017 C1 H17 M6 U24 LGPL-3.0 No Details →
2.8.4 09 Mar 2017 C1 H17 M6 U24 LGPL-3.0 No Details →
2.8.3 09 Mar 2017 C1 H17 M6 U24 LGPL-3.0 No Details →
2.8.2 07 Feb 2017 C1 H17 M6 U24 LGPL-3.0 No Details →
2.8.1 06 Feb 2017 C1 H17 M6 U24 LGPL-3.0 No Details →
2.8.0 21 Jan 2017 C1 H17 M6 U24 non-standard No Details →
2.7.1 11 Sep 2016 C1 H17 M6 U24 non-standard No Details →
2.7.0 10 Sep 2016 C1 H17 M6 U24 non-standard No Details →
2.6.2 12 May 2016 C1 H17 M6 U24 non-standard No Details →
2.6.1 26 Mar 2016 C1 H17 M6 U24 non-standard No Details →
2.6.0 16 Mar 2016 C1 H17 M6 U24 — No Details →
2.5.1 10 Oct 2015 C1 H17 M6 U24 — No Details →
2.5.0 05 Oct 2015 C1 H17 M6 U24 — No Details →
2.4.2 28 May 2015 C1 H17 M6 U24 — No Details →
2.4.1 20 May 2015 C1 H17 M6 U24 — No Details →
2.4.0 20 May 2015 C1 H17 M6 U24 — No Details →
2.3.0 31 Jan 2015 C1 H17 M6 U24 — No Details →
2.2.1 22 Dec 2014 C1 H17 M6 U24 — No Details →
2.2.0 13 Dec 2014 C1 H17 M6 U24 — No Details →
2.1.2 09 Oct 2014 C1 H17 M6 U24 — No Details →
2.1.1 02 Oct 2014 C1 H17 M6 U24 — No Details →
2.1.0 13 Sep 2014 C1 H17 M6 U24 — No Details →
2.0.1 22 Jun 2014 C1 H17 M6 U24 — No Details →
2.0.0 14 Jun 2014 C1 H17 M6 U24 — No Details →
1.7.7 14 May 2014 C1 H17 M6 U24 — No Details →
1.7.6 25 Mar 2014 C1 H17 M6 U24 — No Details →
1.7.5 11 Mar 2014 C1 H17 M6 U24 — No Details →
1.7.4 18 Jan 2014 C1 H17 M6 U24 — No Details →
1.7.3 15 Dec 2013 C1 H17 M6 U24 — No Details →
1.7.2 01 Nov 2013 C1 H17 M6 U24 — No Details →

The newest 120 of 177 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2
  • 2026 50

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 50 of the 52 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for glances

The 5 most severe of 52 vulnerabilities recorded for this package

Search all 52 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-30930: Glances SQL Injection Vulnerability in TimescaleDB Export Module 9.8 critical 4.5.1 10 Mar 2026
CVE-2026-32633: Glances Package Exposes Reusable Downstream Credentials via API Endpoint 9.1 critical 4.5.2 16 Mar 2026
CVE-2026-32633: Glances Package Exposes Reusable Downstream Credentials via API Endpoint 9.1 critical 4.5.2 29 Jun 2026
CVE-2026-32611: Glances Package SQL Injection Vulnerability in DuckDB Export Module 9.1 critical 4.5.2 18 Mar 2026
CVE-2026-62982: Glances OS Command Injection via Incomplete Fix of Nested Stat Values 8.8 high 4.5.6 17 Aug 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About glances

Is glances safe to use?

Vulert records 52 vulnerabilities for glances in PyPI: 1 critical, 19 high, 6 medium and 0 low, plus 26 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is glances's Vulert package health score?

Vulert scores glances 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of glances affected?

Yes. 4.5.8, the version you would install today, has 3 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of glances should I use?

4.5.8 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does glances have?

52 vulnerabilities are recorded for glances in the PyPI ecosystem: 1 critical, 19 high, 6 medium and 0 low, plus 26 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new glances vulnerabilities disclosed?

50 vulnerabilities were recorded for glances in the last 12 months, and the oldest entry in this database dates to 29 Jul 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of glances are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor glances for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the glances version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.