VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

azure-identity: vulnerability history, versions and safety

azure-identity is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 61 releases, from Jun 2024 to Jul 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 M1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all azure-identity vulnerabilities

Vulert verdict on azure-identity 1.26.0 i

Updated on 23 Oct 2026

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

Package health score 88/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 1.26.0 — unaffected i
  • Vulnerabilities on record 2 over 2 years · 1 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 5.5 i
  • With no published fix 0 i
  • Depended on by 1,976 packages i
  • Stars 5,621 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence MIT 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 azure-identity, 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
1.26.0 01 Oct 2026 none MIT — Details →
1.25.3 13 Mar 2026 none MIT — Details →
1.26.0b2 12 Feb 2026 none MIT — Details →
1.25.2 11 Feb 2026 none MIT — Details →
1.26.0b1 07 Nov 2025 none MIT — Details →
1.25.1 06 Oct 2025 none MIT — Details →
1.25.0 12 Sep 2025 none MIT — Details →
1.24.0 07 Aug 2025 none MIT — Details →
1.24.0b1 18 Jul 2025 none MIT — Details →
1.23.1 15 Jul 2025 none MIT — Details →
1.23.0 14 May 2025 none MIT — Details →
1.22.0 06 May 2025 none MIT — Details →
1.21.0 11 Mar 2025 none MIT — Details →
1.20.0 12 Feb 2025 none MIT — Details →
1.19.0 08 Oct 2024 none MIT — Details →
1.18.0 19 Sep 2024 none MIT — Details →
1.18.0b2 09 Aug 2024 none MIT — Details →
1.18.0b1 16 Jul 2024 none MIT — Details →
1.17.1 22 Jun 2024 none MIT — Details →
1.17.0 18 Jun 2024 none MIT — Details →
1.17.0b2 10 Jun 2024 none MIT — Details →
1.16.1 10 Jun 2024 none MIT — Details →
1.17.0b1 13 May 2024 none MIT — Details →
1.16.0 09 Apr 2024 M1 U1 MIT Yes Details →
1.16.0b2 05 Mar 2024 M1 U1 MIT Yes Details →
1.16.0b1 06 Feb 2024 M1 U1 MIT Yes Details →
1.15.0 26 Oct 2023 M1 U1 MIT Yes Details →
1.15.0b2 12 Oct 2023 M1 U1 MIT Yes Details →
1.14.1 09 Oct 2023 M1 U1 MIT Yes Details →
1.15.0b1 12 Sep 2023 M1 U1 MIT Yes Details →
1.14.0 09 Aug 2023 M1 U1 MIT Yes Details →
1.14.0b2 11 Jul 2023 M1 U1 MIT Yes Details →
1.14.0b1 06 Jun 2023 M1 U1 MIT Yes Details →
1.13.0 11 May 2023 M1 U1 MIT Yes Details →
1.13.0b4 11 Apr 2023 M1 U1 MIT Yes Details →
1.13.0b3 07 Mar 2023 M1 U1 MIT Yes Details →
1.13.0b2 07 Feb 2023 M1 U1 MIT Yes Details →
1.13.0b1 10 Jan 2023 M1 U1 MIT Yes Details →
1.12.0 08 Nov 2022 M1 U1 MIT Yes Details →
1.12.0b2 11 Oct 2022 M1 U1 MIT Yes Details →
1.12.0b1 22 Sep 2022 M1 U1 MIT Yes Details →
1.11.0 19 Sep 2022 M1 U1 MIT Yes Details →
1.11.0b3 09 Aug 2022 M1 U1 MIT Yes Details →
1.11.0b2 05 Jul 2022 M1 U1 MIT Yes Details →
1.11.0b1 10 May 2022 M1 U1 MIT Yes Details →
1.10.0 28 Apr 2022 M1 U1 MIT Yes Details →
1.10.0b1 07 Apr 2022 M1 U1 MIT Yes Details →
1.9.0 05 Apr 2022 M1 U1 MIT Yes Details →
1.9.0b1 08 Mar 2022 M1 U1 MIT Yes Details →
1.8.0 01 Mar 2022 M1 U1 MIT Yes Details →
1.8.0b1 08 Feb 2022 M1 U1 MIT Yes Details →
1.7.1 09 Nov 2021 M1 U1 MIT Yes Details →
1.7.0 14 Oct 2021 M1 U1 MIT Yes Details →
1.7.0b4 09 Sep 2021 M1 U1 MIT Yes Details →
1.6.1 19 Aug 2021 M1 U1 MIT Yes Details →
1.7.0b3 10 Aug 2021 M1 U1 MIT Yes Details →
1.7.0b2 08 Jul 2021 M1 U1 MIT Yes Details →
1.7.0b1 08 Jun 2021 M1 U1 MIT Yes Details →
1.6.0 13 May 2021 M1 U1 MIT Yes Details →
1.6.0b3 06 Apr 2021 M1 U1 MIT Yes Details →
1.6.0b2 09 Mar 2021 M1 U1 MIT Yes Details →
1.6.0b1 09 Feb 2021 M1 U1 MIT Yes Details →
1.5.0 11 Nov 2020 M1 U1 MIT Yes Details →
1.5.0b2 08 Oct 2020 M1 U1 MIT Yes Details →
1.4.1 07 Oct 2020 M1 U1 MIT Yes Details →
1.5.0b1 09 Sep 2020 M1 U1 MIT Yes Details →
1.4.0 10 Aug 2020 M1 U1 MIT Yes Details →
1.4.0b7 22 Jul 2020 M1 U1 MIT Yes Details →
1.4.0b6 07 Jul 2020 M1 U1 MIT Yes Details →
1.4.0b5 12 Jun 2020 M1 U1 MIT Yes Details →
1.4.0b4 09 Jun 2020 M1 U1 MIT Yes Details →
1.4.0b3 04 May 2020 M1 U1 MIT Yes Details →
1.4.0b2 07 Apr 2020 M1 U1 MIT Yes Details →
1.3.1 01 Apr 2020 M1 U1 MIT Yes Details →
1.4.0b1 10 Mar 2020 M1 U1 MIT Yes Details →
1.3.0 11 Feb 2020 M1 U1 MIT Yes Details →
1.2.0 14 Jan 2020 M1 U1 MIT Yes Details →
1.1.0 02 Dec 2019 M1 U1 MIT Yes Details →
1.0.1 05 Nov 2019 M1 U1 MIT Yes Details →
1.0.0 30 Oct 2019 M1 U1 MIT Yes Details →
1.0.0b4 07 Oct 2019 M1 U1 MIT Yes Details →
1.0.0b3 10 Sep 2019 M1 U1 MIT Yes Details →
1.0.0b2 05 Aug 2019 M1 U1 MIT Yes Details →
1.0.0b1 28 Jun 2019 M1 U1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for azure-identity

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Azure Identity Libraries and Microsoft Authentication Library Elevation of Privilege Vulnerability 5.5 medium 1.16.1 11 Jun 2024
CVE-2024-35255: Azure Identity Package Elevation of Privilege Vulnerability 5.5 medium 1.16.1 07 Jul 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 azure-identity

Is azure-identity safe to use?

Vulert records 2 vulnerabilities for azure-identity in PyPI: 0 critical, 0 high, 1 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 azure-identity's Vulert package health score?

Vulert scores azure-identity 88/100, which reads as healthy. 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 azure-identity affected?

No. 1.26.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 azure-identity should I use?

1.26.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 azure-identity have?

2 vulnerabilities are recorded for azure-identity in the PyPI ecosystem: 0 critical, 0 high, 1 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 azure-identity vulnerabilities disclosed?

1 vulnerability was recorded for azure-identity in the last 12 months, and the oldest entry in this database dates to 11 Jun 2024. 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 azure-identity 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 azure-identity for upcoming vulnerabilities?

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