CVE-2026-68939

LOWPre-NVD 2.02.0—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (6th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
2.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 2.0Exploit: Elevated riskExposed services: Not assessed

The CVE record names the fixed release — apply it.

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.

CVSS v3
2.0
EG Score
2.0LOWmedium confidence
EG Risk
25
EG Risk 25/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity20% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 18, 2026

Last Modified

September 18, 2026

References (4)

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pyenv2.5.4-1 ... 2.7.1-1 (7 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pyenv2.5.4-1 ... 2.7.1-1 (7 versions)
  • every version on: no fix on record
—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:13 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-05 07:16 UTCEG score recompute
  7. 2026-10-04 23:22 UTCEPSS rescore
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-02 17:56 UTCEPSS rescore
  10. 2026-10-02 01:28 UTCEG score recompute
  11. 2026-10-01 19:50 UTCEPSS rescore
  12. 2026-09-30 15:03 UTCEPSS rescore
  13. 2026-09-28 13:52 UTCEPSS rescore
  14. 2026-09-28 13:31 UTCEG score recompute
  15. 2026-09-27 13:48 UTCEPSS rescore
  16. 2026-09-26 15:59 UTCEPSS rescore
  17. 2026-09-25 07:44 UTCEG score recompute
  18. 2026-09-23 17:54 UTCEPSS rescore
  19. 2026-09-22 01:57 UTCEG score recompute
  20. 2026-09-21 21:09 UTCEPSS rescore
  21. 2026-09-20 20:16 UTCEPSS rescore
  22. 2026-09-18 20:09 UTCEG score recompute
  23. 2026-09-18 19:28 UTCEPSS rescore
  24. 2026-09-17 04:25 UTCEG score recompute
  25. 2026-09-16 14:08 UTCEPSS rescore
Show 31 more
  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-13 22:31 UTCEG score recompute
  3. 2026-09-11 09:37 UTCEPSS rescore
  4. 2026-09-10 16:44 UTCEG score recompute
  5. 2026-09-08 22:01 UTCEPSS rescore
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-07 10:26 UTCEG score recompute
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-05 15:31 UTCEPSS rescore
  10. 2026-09-04 05:07 UTCEPSS rescore
  11. 2026-09-04 02:11 UTCEG score recompute
  12. 2026-09-02 14:12 UTCEPSS rescore
  13. 2026-09-01 13:54 UTCEPSS rescore
  14. 2026-09-01 04:40 UTCEPSS rescore
  15. 2026-08-31 20:18 UTCEG score recompute
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:42 UTCEPSS rescore
  19. 2026-08-28 12:59 UTCEG score recompute
  20. 2026-08-26 14:47 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 06:59 UTCEG score recompute
  23. 2026-08-22 01:12 UTCEG score recompute
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-20 22:56 UTCEPSS rescore
  26. 2026-08-19 17:04 UTCEPSS rescore
  27. 2026-08-18 19:24 UTCEG score recompute
  28. 2026-08-18 19:05 UTCEG score recompute
  29. 2026-08-18 15:19 UTCEG score recompute
  30. 2026-08-18 15:14 UTCEG score recompute
  31. 2026-08-18 15:14 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-68939?
CVE-2026-68939 is a low vulnerability published on August 18, 2026. Pyenv provides simple Python version management. Prior to 2.8.0, isversionsafe() 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,…
When was CVE-2026-68939 disclosed?
CVE-2026-68939 was first published on August 18, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68939 actively exploited?
CVE-2026-68939 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68939?
CVE-2026-68939 has a CVSS base score of 2.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68939?
The CVE record for CVE-2026-68939 names the fix: "This issue is fixed in version 2.8.0."

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-68939

Explore →

Is Your Infrastructure Affected by CVE-2026-68939?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs