VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

ceilometer: vulnerability history, versions and safety

ceilometer is a package in the PyPI ecosystem. Vulert records 3 vulnerabilities for it across 8 releases, from Mar 2019 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded M1 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ceilometer vulnerabilities

Vulert verdict on ceilometer 27.0.0 i

Updated on 23 Oct 2026

Good news: 27.0.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 84/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

What to do: Stay on 27.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 27.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 27.0.0 — unaffected i
  • Vulnerabilities on record 3 over 3 years · 0 in the last year i
  • Latest disclosure 13 May 2022 i
  • Highest CVSS 4.0 i
  • With no published fix 0 i
  • Depended on by 2 packages i
  • Last release this month i
  • Licence non-standard 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 ceilometer, 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
27.0.0 30 Sep 2026 none non-standard — Details →
27.0.0.0rc1 09 Sep 2026 none non-standard — Details →
24.0.2 20 Jul 2026 none non-standard — Details →
26.0.0 01 Apr 2026 none non-standard — Details →
26.0.0.0rc1 12 Mar 2026 none non-standard — Details →
23.0.2 28 Jan 2026 none non-standard — Details →
25.0.0 01 Oct 2025 none Apache-2.0 — Details →
25.0.0.0rc1 15 Sep 2025 none Apache-2.0 — Details →
23.0.1 04 Sep 2025 none Apache-2.0 — Details →
24.0.1 04 Sep 2025 none Apache-2.0 — Details →
22.0.1 04 Sep 2025 none Apache-2.0 — Details →
21.0.1 28 Apr 2025 none Apache-2.0 — Details →
24.0.0 02 Apr 2025 none Apache-2.0 — Details →
24.0.0.0rc1 17 Mar 2025 none Apache-2.0 — Details →
23.0.0 02 Oct 2024 none non-standard — Details →
23.0.0.0rc1 16 Sep 2024 none non-standard — Details →
22.0.0 03 Apr 2024 none non-standard — Details →
22.0.0.0rc1 15 Mar 2024 none non-standard — Details →
21.0.0 04 Oct 2023 none non-standard — Details →
21.0.0.0rc1 15 Sep 2023 none non-standard — Details →
18.1.0 01 Jun 2023 none non-standard — Details →
19.1.0 01 Jun 2023 none non-standard — Details →
20.0.0 22 Mar 2023 none non-standard — Details →
20.0.0.0rc1 03 Mar 2023 none non-standard — Details →
17.0.2 18 Jan 2023 none non-standard — Details →
19.0.0 05 Oct 2022 none non-standard — Details →
19.0.0.0rc1 13 Sep 2022 none non-standard — Details →
18.0.0 30 Mar 2022 none non-standard — Details →
18.0.0.0rc1 08 Mar 2022 none non-standard — Details →
17.0.1 10 Feb 2022 none non-standard — Details →
16.0.1 10 Feb 2022 none non-standard — Details →
15.1.0 24 Jan 2022 none non-standard — Details →
17.0.0 06 Oct 2021 none non-standard — Details →
17.0.0.0rc1 15 Sep 2021 none non-standard — Details →
14.1.0 27 Jul 2021 none non-standard — Details →
16.0.0 14 Apr 2021 none non-standard — Details →
16.0.0.0rc1 22 Mar 2021 none non-standard — Details →
13.1.2 01 Feb 2021 none non-standard — Details →
15.0.0 14 Oct 2020 none non-standard — Details →
15.0.0.0rc1 24 Sep 2020 none non-standard — Details →
12.1.1 20 Jul 2020 none non-standard — Details →
13.1.1 15 Jun 2020 none non-standard — Details →
14.0.0 13 May 2020 none non-standard — Details →
14.0.0.0rc1 22 Apr 2020 none non-standard — Details →
12.1.0 27 Feb 2020 none non-standard — Details →
11.1.0 27 Feb 2020 M1 U2 non-standard Yes Details →
13.1.0 27 Feb 2020 none non-standard — Details →
13.0.0 16 Oct 2019 none non-standard — Details →
13.0.0.0rc2 10 Oct 2019 none non-standard — Details →
13.0.0.0rc1 26 Sep 2019 none non-standard — Details →
9.0.7 26 Apr 2019 M1 U2 non-standard Yes Details →
12.0.0 10 Apr 2019 M1 U2 non-standard Yes Details →
12.0.0.0rc1 21 Mar 2019 none non-standard — Details →
11.0.1 15 Oct 2018 M1 U2 non-standard Yes Details →
9.0.6 10 Sep 2018 M1 U2 non-standard Yes Details →
8.1.5 10 Sep 2018 M1 U2 non-standard Yes Details →
10.0.1 10 Sep 2018 M1 U2 non-standard Yes Details →
11.0.0 10 Sep 2018 M1 U2 non-standard Yes Details →

All 58 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 2
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for ceilometer

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-3830: Ceilometer Prints Sensitive Configuration Data to Log 4.0 medium 12.0.0.0rc1 13 May 2022
CVE-2019-3830: Information Exposure in ceilometer N/A unrated 12.0.0.0rc1 26 Mar 2019
CVE-2019-3830: Information Exposure in ceilometer N/A unrated 12.0.0.0rc1 26 Mar 2019

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 ceilometer

Is ceilometer safe to use?

Vulert records 3 vulnerabilities for ceilometer in PyPI: 0 critical, 0 high, 1 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is ceilometer's Vulert package health score?

Vulert scores ceilometer 84/100, which reads as in good shape. 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).

Is the latest version of ceilometer affected?

No. 27.0.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of ceilometer should I use?

27.0.0 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 ceilometer have?

3 vulnerabilities are recorded for ceilometer in the PyPI ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 2 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 ceilometer vulnerabilities disclosed?

0 vulnerabilities were recorded for ceilometer in the last 12 months, and the oldest entry in this database dates to 26 Mar 2019. 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 ceilometer 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 ceilometer for upcoming vulnerabilities?

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