CVE-2022-35861: pyenv 1.2.24 through 2.3.2 allows local users to gain privileges via a .python-version file in the current wor

Routine

HIGH 7.8UPGRADE

CVE-2022-35861 is a high-severity flaw (CVSS 7.8) affecting pyenv. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

pyenv 1.2.24 through 2.3.2 allows local users to gain privileges via a .python-version file in the current working directory. An attacker can craft a Python version string in .python-version to execute shims under their control. (Shims are executables that pass a command along to a specific version of pyenv. The version string is used to construct the path to the command, and there is no validation of whether the version specified is a valid vers

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 79%)
CISA exploited list	No
Weakness	CWE-22
Published	2022-07-17
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: pyenv

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-07-17 17:15 UTCPublished CVE record published
2026-06-17 04:52 UTCUpdated Record last modified

pyenv pyenv UPGRADE

Affected: >= 1.2.24 and <= 2.3.2

Fixed in: newer than 2.3.2

Safe to downgrade to: a release before 1.2.24

1. Check installed version

apt-cache policy pyenv || rpm -q pyenv || pyenv --version

2. UPGRADE to newer than 2.3.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade pyenv

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade pyenv

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.2.24 (Debian / Ubuntu)

apt-cache madison pyenv sudo apt install pyenv=<VERSION_BEFORE_1.2.24> sudo apt-mark hold pyenv

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list pyenv sudo dnf downgrade pyenv-<VERSION_BEFORE_1.2.24> sudo dnf versionlock add pyenv

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-35861?

pyenv: upgrade to newer than 2.3.2. Exact commands for each OS are on this page.

Is CVE-2022-35861 being exploited?

CVE-2022-35861 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-35861 affect?

CVE-2022-35861 affects pyenv. Severity is high (CVSS 7.8). pyenv 1.2.24 through 2.3.2 allows local users to gain privileges via a .python-version file in the current working directory. An attacker can craft a Python version string in .python-version to execute shims under their control. (Shims are

How urgent is CVE-2022-35861?

Priority 33/100. High severity

Software pages

Python vulnerabilities

References

← Back to latest CVEs