Vulnerability Description
Pyenv provides simple Python version management. Prior to 2.8.0, is_version_safe() in libexec/pyenv-version-file-read accepts shell glob metacharacters in .python-version values, and unquoted PYENV_VERSION expansion in libexec/pyenv-version-name, libexec/pyenv-which, libexec/pyenv-prefix, libexec/pyenv-local, libexec/pyenv-global, libexec/pyenv-version, and libexec/pyenv-versions pathname-expands the value against the current directory, allowing a matching attacker-controlled file to silently select a different installed interpreter or version. This issue is fixed in version 2.8.0.
Related Weaknesses (CWE)
References
- https://github.com/pyenv/pyenv/commit/95df7dbc7b34595b47c9b922de198547effda819
- https://github.com/pyenv/pyenv/releases/tag/v2.8.0
- https://github.com/pyenv/pyenv/security/advisories/GHSA-g478-f579-9vp9
- https://github.com/pyenv/pyenv/security/advisories/GHSA-g478-f579-9vp9
FAQ
What is CVE-2026-68939?
CVE-2026-68939 is a documented vulnerability. Pyenv provides simple Python version management. Prior to 2.8.0, is_version_safe() in libexec/pyenv-version-file-read accepts shell glob metacharacters in .python-version values, and unquoted PYENV_VE...
How severe is CVE-2026-68939?
CVSS scoring is not yet available for CVE-2026-68939. Check NVD for updates.
Is there a patch for CVE-2026-68939?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.