VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

vitrage: vulnerability history, versions and safety

vitrage is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 54 releases, from Feb 2026 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 29 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all vitrage vulnerabilities

Vulert verdict on vitrage 15.0.1 i

Updated on 23 Oct 2026

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

Package health score 65/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

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

  • Current release 15.0.1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 29 Jun 2026 i
  • Highest CVSS 9.1 i
  • With no published fix 0 i
  • Last release 12 months ago i
  • Licence Apache-2.0 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 vitrage, 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
15.0.1 03 Oct 2025 none Apache-2.0 — Details →
14.0.1 03 Oct 2025 none Apache-2.0 — Details →
12.0.1 03 Oct 2025 none Apache-2.0 — Details →
13.0.1 03 Oct 2025 none Apache-2.0 — Details →
15.0.0 01 Oct 2025 C1 Apache-2.0 Yes Details →
15.0.0.0rc1 15 Sep 2025 C1 Apache-2.0 Yes Details →
14.0.0 02 Apr 2025 none Apache-2.0 — Details →
14.0.0.0rc1 17 Mar 2025 none Apache-2.0 — Details →
13.0.0 02 Oct 2024 none non-standard — Details →
13.0.0.0rc1 16 Sep 2024 none non-standard — Details →
12.0.0 03 Apr 2024 U1 non-standard Yes Details →
12.0.0.0rc2 02 Apr 2024 U1 non-standard Yes Details →
12.0.0.0rc1 14 Mar 2024 U1 non-standard Yes Details →
11.0.0 04 Oct 2023 U1 non-standard Yes Details →
11.0.0.0rc1 15 Sep 2023 U1 non-standard Yes Details →
10.0.0 22 Mar 2023 U1 non-standard Yes Details →
10.0.0.0rc1 03 Mar 2023 U1 non-standard Yes Details →
9.0.0 02 Aug 2022 U1 non-standard Yes Details →
8.0.1 16 Mar 2022 U1 non-standard Yes Details →
8.0.0 27 Jan 2022 U1 non-standard Yes Details →
7.5.0 03 Aug 2021 U1 non-standard Yes Details →
7.4.0 11 Feb 2021 U1 non-standard Yes Details →
7.3.0 24 Sep 2020 U1 non-standard Yes Details →
7.2.0 10 Sep 2020 U1 non-standard Yes Details →
4.3.2 20 Jul 2020 U1 non-standard Yes Details →
5.0.2 15 Jun 2020 U1 non-standard Yes Details →
7.1.0 27 Apr 2020 U1 non-standard Yes Details →
7.0.0 08 Apr 2020 U1 non-standard Yes Details →
6.0.1 18 Mar 2020 U1 non-standard Yes Details →
6.0.0 13 Feb 2020 U1 non-standard Yes Details →
5.0.1 17 Oct 2019 U1 non-standard Yes Details →
5.0.0 09 Aug 2019 U1 non-standard Yes Details →
1.8.3 16 Apr 2019 U1 non-standard Yes Details →
4.3.1 03 Apr 2019 U1 non-standard Yes Details →
4.3.0 21 Mar 2019 U1 non-standard Yes Details →
4.2.0 07 Mar 2019 U1 non-standard Yes Details →
4.1.0 25 Feb 2019 U1 non-standard Yes Details →
4.0.0 09 Jan 2019 U1 non-standard Yes Details →
3.3.0 08 Jan 2019 U1 non-standard Yes Details →
3.2.0 23 Aug 2018 U1 non-standard Yes Details →
3.1.0 09 Aug 2018 U1 non-standard Yes Details →
3.0.0 11 Jun 2018 U1 non-standard Yes Details →
2.3.0 15 May 2018 U1 non-standard Yes Details →
2.2.0 21 Feb 2018 U1 non-standard Yes Details →
2.1.0 08 Feb 2018 U1 non-standard Yes Details →
2.0.0 26 Jan 2018 U1 non-standard Yes Details →
1.8.2 27 Oct 2017 U1 non-standard Yes Details →
1.8.1 21 Aug 2017 U1 non-standard Yes Details →
1.8.0 09 Aug 2017 U1 non-standard Yes Details →
1.7.0 27 Jul 2017 U1 non-standard Yes Details →
1.5.2 08 Jun 2017 U1 non-standard Yes Details →
1.6.0 08 Jun 2017 U1 non-standard Yes Details →
1.5.1 16 Feb 2017 U1 non-standard Yes Details →
1.5.0 02 Feb 2017 U1 non-standard Yes Details →
1.4.0 25 Jan 2017 U1 non-standard Yes Details →
1.3.0 26 Sep 2016 U1 non-standard Yes Details →
1.2.0 22 Sep 2016 U1 non-standard Yes Details →
1.1.0 25 Aug 2016 U1 non-standard Yes Details →
0.7.0 24 Aug 2016 U1 non-standard Yes Details →
1.0.0 24 Aug 2016 U1 non-standard Yes Details →
0.2.0 27 Apr 2016 U1 non-standard Yes Details →
0.0.1.dev451 17 Apr 2016 U1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for vitrage

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-28370: OpenStack Vitrage Unauthorized Access Leading to Eval Injection 9.1 critical 15.0.1 27 Feb 2026
CVE-2026-28370: Vitrage API Unauthorized Access Leading to Eval Injection 9.1 critical 12.0.1 29 Jun 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 vitrage

Is vitrage safe to use?

Vulert records 2 vulnerabilities for vitrage in PyPI: 1 critical, 0 high, 0 medium and 0 low, plus 1 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 vitrage's Vulert package health score?

Vulert scores vitrage 65/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).

Is the latest version of vitrage affected?

No. 15.0.1, 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 vitrage should I use?

15.0.1 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 vitrage have?

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

2 vulnerabilities were recorded for vitrage in the last 12 months, and the oldest entry in this database dates to 27 Feb 2026. 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 vitrage 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 vitrage for upcoming vulnerabilities?

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