VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

poetry: vulnerability history, versions and safety

poetry is a package in the PyPI ecosystem. Vulert records 10 vulnerabilities for it across 113 releases, from Mar 2022 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
10 vulnerabilities recorded C1 H3 L1 U5
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all poetry vulnerabilities

Vulert verdict on poetry 2.5.1 i

Updated on 23 Oct 2026

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

Package health score 72/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 2.5.1 — unaffected i
  • Vulnerabilities on record 10 over 4 years · 4 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 302 packages i
  • Stars 34,313 i
  • OpenSSF scorecard 3/10 i
  • Last release 1 month ago 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 poetry, 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
2.5.1 20 Sep 2026 none MIT — Details →
2.5.0 19 Sep 2026 none MIT — Details →
2.4.3 05 Sep 2026 none MIT — Details →
2.4.2 29 Aug 2026 none MIT — Details →
2.4.1 09 May 2026 none MIT — Details →
2.4.0 03 May 2026 none MIT — Details →
2.3.4 12 Apr 2026 none MIT — Details →
2.3.3 29 Mar 2026 L1 U1 MIT Yes Details →
2.3.2 01 Feb 2026 H1 L1 U2 MIT Yes Details →
2.3.1 20 Jan 2026 H1 L1 U2 MIT Yes Details →
2.3.0 18 Jan 2026 H1 L1 U2 MIT Yes Details →
2.2.1 21 Sep 2025 H1 L1 U2 MIT Yes Details →
2.2.0 14 Sep 2025 H1 L1 U2 MIT Yes Details →
2.1.4 05 Aug 2025 H1 L1 U2 MIT Yes Details →
2.1.3 04 May 2025 H1 L1 U2 MIT Yes Details →
2.1.2 29 Mar 2025 H1 L1 U2 MIT Yes Details →
2.1.1 16 Feb 2025 H1 L1 U2 MIT Yes Details →
2.1.0 15 Feb 2025 H1 L1 U2 MIT Yes Details →
2.0.1 12 Jan 2025 H1 L1 U2 MIT Yes Details →
2.0.0 05 Jan 2025 H1 L1 U2 MIT Yes Details →
1.8.5 06 Dec 2024 H1 L1 U2 MIT Yes Details →
1.8.4 14 Oct 2024 H1 L1 U2 MIT Yes Details →
1.8.3 08 May 2024 H1 L1 U2 MIT Yes Details →
1.8.2 02 Mar 2024 H1 L1 U2 MIT Yes Details →
1.8.1 26 Feb 2024 H1 L1 U2 MIT Yes Details →
1.8.0 25 Feb 2024 H1 L1 U2 MIT Yes Details →
1.7.1 16 Nov 2023 H1 L1 U2 MIT Yes Details →
1.7.0 03 Nov 2023 H1 L1 U2 MIT Yes Details →
1.6.1 21 Aug 2023 H1 L1 U2 MIT Yes Details →
1.6.0 20 Aug 2023 H1 L1 U2 MIT Yes Details →
1.5.1 29 May 2023 H1 L1 U2 MIT Yes Details →
1.5.0 19 May 2023 H1 L1 U2 MIT Yes Details →
1.4.2 02 Apr 2023 H1 L1 U2 MIT Yes Details →
1.4.1 19 Mar 2023 H1 L1 U2 MIT Yes Details →
1.4.0 27 Feb 2023 H1 L1 U2 MIT Yes Details →
1.3.2 10 Jan 2023 L1 U1 MIT Yes Details →
1.3.1 12 Dec 2022 L1 U1 MIT Yes Details →
1.3.0 09 Dec 2022 L1 U1 MIT Yes Details →
1.2.2 10 Oct 2022 L1 U1 MIT Yes Details →
1.2.1 16 Sep 2022 L1 U1 MIT Yes Details →
1.2.0 31 Aug 2022 L1 U1 MIT Yes Details →
1.2.0rc2 26 Aug 2022 L1 U1 MIT Yes Details →
1.2.0rc1 23 Aug 2022 L1 U1 MIT Yes Details →
1.1.15 22 Aug 2022 L1 U1 MIT Yes Details →
1.2.0b3 13 Jul 2022 L1 U1 MIT Yes Details →
1.1.14 08 Jul 2022 L1 U1 MIT Yes Details →
1.2.0b2 06 Jun 2022 L1 U1 MIT Yes Details →
1.2.0b1 17 Mar 2022 L1 U1 MIT Yes Details →
1.1.13 10 Feb 2022 L1 U1 MIT Yes Details →
1.1.12 28 Nov 2021 L1 U1 MIT Yes Details →
1.1.11 04 Oct 2021 L1 U1 MIT Yes Details →
1.1.10 21 Sep 2021 L1 U1 MIT Yes Details →
1.1.9 18 Sep 2021 L1 U1 MIT Yes Details →
1.1.8 19 Aug 2021 C1 H2 L1 U4 MIT Yes Details →
1.2.0a2 01 Aug 2021 L1 U1 MIT Yes Details →
1.1.7 25 Jun 2021 C1 H2 L1 U4 MIT Yes Details →
1.2.0a1 21 May 2021 L1 U1 MIT Yes Details →
1.1.6 14 Apr 2021 C1 H2 L1 U4 MIT Yes Details →
1.1.5 04 Mar 2021 C1 H2 L1 U4 MIT Yes Details →
1.1.4 23 Oct 2020 C1 H2 L1 U4 MIT Yes Details →
1.1.3 14 Oct 2020 C1 H2 L1 U4 MIT Yes Details →
1.1.2 06 Oct 2020 C1 H2 L1 U4 MIT Yes Details →
1.1.1 05 Oct 2020 C1 H2 L1 U4 MIT Yes Details →
1.1.0 01 Oct 2020 C1 H2 L1 U4 MIT Yes Details →
1.1.0rc1 25 Sep 2020 C1 H2 L1 U4 MIT Yes Details →
1.1.0b4 22 Sep 2020 C1 H2 L1 U4 MIT Yes Details →
1.1.0b3 18 Sep 2020 C1 H2 L1 U4 MIT Yes Details →
1.1.0b2 24 Jul 2020 C1 H2 L1 U4 MIT Yes Details →
1.1.0b1 24 Jul 2020 C1 H2 L1 U4 MIT Yes Details →
1.0.10 21 Jul 2020 C1 H2 L1 U4 MIT Yes Details →
1.1.0a3 10 Jul 2020 C1 H2 L1 U4 MIT Yes Details →
1.1.0a2 26 Jun 2020 C1 H2 L1 U4 MIT Yes Details →
1.0.9 09 Jun 2020 C1 H2 L1 U4 MIT Yes Details →
1.0.8 05 Jun 2020 C1 H2 L1 U4 MIT Yes Details →
1.0.7 05 Jun 2020 C1 H2 L1 U4 MIT Yes Details →
1.0.6 05 Jun 2020 C1 H2 L1 U4 MIT Yes Details →
1.1.0a1 27 Mar 2020 C1 H2 L1 U4 MIT Yes Details →
1.0.5 29 Feb 2020 C1 H2 L1 U4 MIT Yes Details →
1.0.4 28 Feb 2020 C1 H2 L1 U4 MIT Yes Details →
1.0.3 31 Jan 2020 C1 H2 L1 U4 MIT Yes Details →
1.0.2 10 Jan 2020 C1 H2 L1 U4 MIT Yes Details →
1.0.1 10 Jan 2020 C1 H2 L1 U4 MIT Yes Details →
1.0.0 12 Dec 2019 C1 H2 L1 U4 MIT Yes Details →
1.0.0b9 07 Dec 2019 C1 H2 L1 U4 MIT Yes Details →
1.0.0b8 26 Nov 2019 C1 H2 L1 U4 MIT Yes Details →
1.0.0b7 22 Nov 2019 C1 H2 L1 U4 MIT Yes Details →
1.0.0b6 20 Nov 2019 C1 H2 L1 U4 MIT Yes Details →
1.0.0b5 15 Nov 2019 C1 H2 L1 U4 MIT Yes Details →
1.0.0b4 08 Nov 2019 C1 H2 L1 U4 MIT Yes Details →
1.0.0b3 25 Oct 2019 C1 H2 L1 U4 MIT Yes Details →
1.0.0b2 11 Oct 2019 C1 H2 L1 U4 MIT Yes Details →
1.0.0b1 09 Aug 2019 C1 H2 L1 U4 MIT Yes Details →
1.0.0a5 15 Jul 2019 C1 H2 L1 U4 MIT Yes Details →
0.12.17 03 Jul 2019 C1 H2 L1 U4 MIT Yes Details →
1.0.0a4 11 Jun 2019 C1 H2 L1 U4 MIT Yes Details →
1.0.0a3 26 May 2019 C1 H2 L1 U4 MIT Yes Details →
0.12.16 17 May 2019 C1 H2 L1 U4 MIT Yes Details →
0.12.15 03 May 2019 C1 H2 L1 U4 MIT Yes Details →
0.12.14 26 Apr 2019 C1 H2 L1 U4 MIT Yes Details →
0.12.13 26 Apr 2019 C1 H2 L1 U4 MIT Yes Details →
0.12.12 11 Apr 2019 C1 H2 L1 U4 — Yes Details →
1.0.0a2 14 Jan 2019 C1 H2 L1 U4 — Yes Details →
0.12.11 13 Jan 2019 C1 H2 L1 U4 — Yes Details →
1.0.0a1 08 Dec 2018 C1 H2 L1 U4 — Yes Details →
1.0.0a0 08 Dec 2018 C1 H2 L1 U4 — Yes Details →
0.12.10 22 Nov 2018 C1 H2 L1 U4 — Yes Details →
0.12.9 19 Nov 2018 C1 H2 L1 U4 — Yes Details →
0.12.8 13 Nov 2018 C1 H2 L1 U4 — Yes Details →
0.12.7 08 Nov 2018 C1 H2 L1 U4 — Yes Details →
0.12.6 05 Nov 2018 C1 H2 L1 U4 — Yes Details →
0.12.5 26 Oct 2018 C1 H2 L1 U4 — Yes Details →
0.12.4 21 Oct 2018 C1 H2 L1 U4 — Yes Details →
0.12.3 18 Oct 2018 C1 H2 L1 U4 — Yes Details →
0.12.2 17 Oct 2018 C1 H2 L1 U4 — Yes Details →
0.12.1 17 Oct 2018 C1 H2 L1 U4 — Yes Details →
0.12.0 17 Oct 2018 C1 H2 L1 U4 — Yes Details →
0.12.0a5 16 Oct 2018 C1 H2 L1 U4 — Yes Details →
0.12.0a4 16 Oct 2018 C1 H2 L1 U4 — Yes Details →
0.12.0a3 08 Oct 2018 C1 H2 L1 U4 — Yes Details →
0.12.0a2 18 Sep 2018 C1 H2 L1 U4 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 6
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for poetry

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-26184: Untrusted Search Path in Poetry before v1.1.9 9.8 critical 1.1.9 23 Mar 2022
CVE-2022-36069: Poetry Argument Injection can lead to Local Code Execution in poetry 7.3 high 1.1.9 16 Sep 2022
CVE-2022-36070: Poetry vulnerable to Untrusted Search Path leading to Local Code Execution on Windows 7.3 high 1.1.9 11 Oct 2022
CVE-2022-36070: Poetry Dependency Manager Arbitrary Code Execution Vulnerability 7.3 high 1.1.9 07 Sep 2022
CVE-2026-34591: Poetry Arbitrary File Write Vulnerability Due to Wheel Path Traversal 7.1 high 2.3.3 01 Apr 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 poetry

Is poetry safe to use?

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

Vulert scores poetry 72/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 poetry affected?

No. 2.5.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 poetry should I use?

2.5.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 poetry have?

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

4 vulnerabilities were recorded for poetry in the last 12 months, and the oldest entry in this database dates to 21 Mar 2022. 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 poetry 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 poetry for upcoming vulnerabilities?

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