Is CVE-2026-34591 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-34591 being exploited in the wild.

How severe is CVE-2026-34591?

Medium severity, with a CVSS score of 6.5, published 2 April 2026.

Which products and versions are affected?

poetry (PyPI) >= 1.4.0, <= 2.3.2, ECOSYSTEM:introduced=1.4.0,fixed=2.3.3.

Is there a fix for CVE-2026-34591?

Yes. poetry (PyPI): upgrade to 2.3.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-34591 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-34591?

Check whether you run poetry (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-34591: python-poetry Poetry path traversal in wheel installer

Q: Is there a fix for CVE-2026-34591?

Yes. poetry (PyPI): upgrade to 2.3.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-34591 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-34591?

Check whether you run poetry (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-34591 · Severity: medium · CVSS 6.5 · Published 2026-04-02

Poetry, a popular dependency manager for Python, is vulnerable to a security flaw that allows a malicious package to write files to unauthorized locations on a user's computer. If a developer or automated system installs a specially crafted 'wheel' package, the software can bypass security checks and overwrite sensitive system or configuration files. This could lead to system instability or provide a foothold for further attacks on development environments and CI/CD pipelines.

Technologies: poetry (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-34591 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-34591 being exploited in the wild.
How severe is CVE-2026-34591?: Medium severity, with a CVSS score of 6.5, published 2 April 2026.
Which products and versions are affected?: poetry (PyPI) >= 1.4.0, <= 2.3.2, ECOSYSTEM:introduced=1.4.0,fixed=2.3.3.
Is there a fix for CVE-2026-34591?: Yes. poetry (PyPI): upgrade to 2.3.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-34591 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-34591?: Check whether you run poetry (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

poetry (PyPI): upgrade to 2.3.3 or later
```
pip install "poetry>=2.3.3"
```

Technical details

A path traversal vulnerability (CWE-22) exists in Poetry's wheel installer component. The `write_to_fs` function in `src/poetry/installation/wheel_installer.py` failed to perform containment checks on file paths within a wheel archive. By including `../` sequences in a crafted wheel, an attacker can cause Poetry to write files to arbitrary locations on the filesystem with the permissions of the Poetry process. While installation alone typically does not execute code, the ability to overwrite configuration files or binaries can lead to remote code execution. The issue is patched in version 2.3.3 by resolving and validating target paths to ensure they remain within the intended installation scheme directory.

Affected products

python-poetry Poetry >= 1.4.0, < 2.3.3

Identifiers

CVE-2026-34591
GHSA-2599-h6xx-hpxp
PYSEC-2026-2260

Timeline

2026-03-29: patched: Fix merged in pull request #10792 and released in version 2.3.3
2026-03-31: advisory: GitHub Security Advisory GHSA-2599-h6xx-hpxp published
2026-04-02: disclosed: CVE-2026-34591 published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.