Skip to main content
No exploitation reportedFix available

CVE-2022-36070

No exploitation reported by the sources we read.

  • Published2022-09-07
  • Fixed in1.1.9
  • WeaknessCWE-426

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Poetry is a dependency manager for Python. To handle dependencies that come from a Git repository, Poetry executes various commands, e.g. `git config`. These commands are being executed using the executable’s name and not its absolute path. This can lead to the execution of untrusted code due to the way Windows resolves executable names to paths. Unlike Linux-based operating systems, Windows searches for the executable in the current directory first and looks in the paths that are defined in the `PATH` environment variable afterward. This vulnerability can lead to Arbitrary Code Execution, which would lead to the takeover of the system. If a developer is exploited, the attacker could steal credentials or persist their access. If the exploit happens on a server, the attackers could use their access to attack other internal systems. Since this vulnerability requires a fair amount of user interaction, it is not as dangerous as a remotely exploitable one. However, it still puts developers at risk when dealing with untrusted files in a way they think is safe. The victim could also not protect themself by vetting any Git or Poetry config files that might be present in the directory, because the behavior is undocumented. Versions 1.1.9 and 1.2.0b1 contain patches for this issue.

Timeline

dates in UTC
  1. 2022-09-0719:15CVE publishedNVD

Versions per branch

NVD · OSV
Python-poetry poetryversion to verify
BranchAffectedFixed in
1.1< 1.1.91.1.9
1.2= 1.2.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • python-poetry poetry
    Affected
    • = < 1.1.9no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2022-09-07

Fix

  1. Update Python-poetry poetry to 1.1.9

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionnone2025-04-23
  • CNACVSS 3.17.3known since 2026-10-23
  • NVDCVSS 3.17.3read 2026-10-23
  • CNAweakness (CWE)CWE-426known since 2026-10-23
  • FIRST EPSSEPSS score0.4 %2026-11-18
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2022-10-11

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Published
2022-09-07
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-j4j9-7hg9-97g6

Frequently asked questions

What is CVE-2022-36070?

Poetry is a dependency manager for Python. To handle dependencies that come from a Git repository, Poetry executes various commands, e.g. `git config`. These commands are being executed using the executable’s name and not its absolute path. This can lead to the execution of untrusted code due to the way Windows resolves executable names to paths. Unlike Linux-based operating systems, Windows searches for the executable in the current directory first and looks in the paths that are defined in the `PATH` environment variable afterward. This vulnerability can lead to Arbitrary Code Execution, which would lead to the takeover of the system. If a developer is exploited, the attacker could steal credentials or persist their access. If the exploit happens on a server, the attackers could use their access to attack other internal systems. Since this vulnerability requires a fair amount of user interaction, it is not as dangerous as a remotely exploitable one. However, it still puts developers at risk when dealing with untrusted files in a way they think is safe. The victim could also not protect themself by vetting any Git or Poetry config files that might be present in the directory, because the behavior is undocumented. Versions 1.1.9 and 1.2.0b1 contain patches for this issue.

Is CVE-2022-36070 actively exploited?

Active exploitation of CVE-2022-36070 has not been confirmed. Its EPSS score was 0.4% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-36070?

CVE-2022-36070 has a CVSS v3 base score of 7.3 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H.

Running poetry? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record