CVE-2026-67322

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-01. the CNA's CVSS baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 4 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

GitPython before 3.1.52 is vulnerable to environment-variable exfiltration in Repo.clone_from(). The caller-supplied remote URL is passed through Git.polish_url(), which on non-Cygwin platforms calls os.path.expandvars() on the URL before invoking git clone. An attacker who controls the clone URL can embed $NAME or ${NAME} tokens that are expanded to the values of the hosting process's environment variables (e.g., AWS_SECRET_ACCESS_KEY or GITHUB_TOKEN). The resulting URL, now containing the secret, is transmitted over the network to an attacker-controlled host during the clone attempt, disclosing the secret.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

August 1, 2026

Last Modified

August 14, 2026

Advisory Details (2)

Auto-updated Aug 1, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

GitPython before 3.1.52 Environment Variable Exfiltration via clone_from | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitpython-before-environment-variable-exfiltration-via-clone-from
github Patch Available🟡 PoC Available

Environment-variable exfiltration via os.path.expandvars() on Repo.clone_from() URL · Advisory · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-rwj8-pgh3-r573

Vendor Advisories for CVE-2026-67322(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatllvm21-main-21.1.8-8.hum12026-07-26redhat
redhatswift-lang-main-6.3.3-0.1.1.hum12026-07-25redhat
redhatllvm-main-22.1.8-4.1.hum12026-07-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.14-1 ... 3.1.50-1 (14 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.30-1 ... 3.1.50-1 (10 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-1——
PyPI(1)
PackageVulnerable rangeFixed inDependents
gitpython0.1.7 ... 3.1.9 (104 versions)3.1.52—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 41× in last 7d / 117× 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.

Showing the most recent 100 of 117 total refreshes for this CVE.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 22:10 UTCVendor advisory
  3. 2026-08-20 22:10 UTCGHSA enrichment
  4. 2026-08-20 10:35 UTCVendor advisory
  5. 2026-08-20 10:35 UTCGHSA enrichment
  6. 2026-08-19 23:09 UTCEG score recompute
  7. 2026-08-19 23:09 UTCVendor advisory
  8. 2026-08-19 23:09 UTCGHSA enrichment
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 11:43 UTCVendor advisory
  11. 2026-08-19 11:43 UTCGHSA enrichment
  12. 2026-08-19 00:17 UTCEG score recompute
  13. 2026-08-19 00:17 UTCVendor advisory
  14. 2026-08-19 00:17 UTCGHSA enrichment
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-18 12:51 UTCVendor advisory
  17. 2026-08-18 12:51 UTCGHSA enrichment
  18. 2026-08-18 01:22 UTCEG score recompute
  19. 2026-08-18 01:22 UTCVendor advisory
  20. 2026-08-18 01:22 UTCGHSA enrichment
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-17 13:45 UTCVendor advisory
  23. 2026-08-17 13:45 UTCGHSA enrichment
  24. 2026-08-17 02:20 UTCEG score recompute
  25. 2026-08-17 02:20 UTCVendor advisory
Show 75 more
  1. 2026-08-17 02:20 UTCGHSA enrichment
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 14:54 UTCVendor advisory
  4. 2026-08-16 14:54 UTCGHSA enrichment
  5. 2026-08-16 03:28 UTCEG score recompute
  6. 2026-08-16 03:28 UTCVendor advisory
  7. 2026-08-16 03:28 UTCGHSA enrichment
  8. 2026-08-15 16:03 UTCVendor advisory
  9. 2026-08-15 16:03 UTCGHSA enrichment
  10. 2026-08-15 04:37 UTCEG score recompute
  11. 2026-08-15 04:37 UTCVendor advisory
  12. 2026-08-15 04:37 UTCGHSA enrichment
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 17:11 UTCEG score recompute
  15. 2026-08-14 17:11 UTCVendor advisory
  16. 2026-08-14 17:11 UTCGHSA enrichment
  17. 2026-08-14 06:52 UTCEG score recompute
  18. 2026-08-14 06:52 UTCVendor advisory
  19. 2026-08-14 06:52 UTCGHSA enrichment
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-13 19:26 UTCVendor advisory
  22. 2026-08-13 19:26 UTCGHSA enrichment
  23. 2026-08-13 08:00 UTCVendor advisory
  24. 2026-08-13 08:00 UTCGHSA enrichment
  25. 2026-08-12 20:35 UTCEG score recompute
  26. 2026-08-12 20:35 UTCVendor advisory
  27. 2026-08-12 20:35 UTCGHSA enrichment
  28. 2026-08-12 13:51 UTCEPSS rescore
  29. 2026-08-12 09:09 UTCVendor advisory
  30. 2026-08-12 09:09 UTCGHSA enrichment
  31. 2026-08-11 21:43 UTCEG score recompute
  32. 2026-08-11 21:43 UTCVendor advisory
  33. 2026-08-11 21:43 UTCGHSA enrichment
  34. 2026-08-11 10:17 UTCEG score recompute
  35. 2026-08-11 10:17 UTCVendor advisory
  36. 2026-08-11 10:17 UTCGHSA enrichment
  37. 2026-08-11 00:00 UTCEPSS rescore
  38. 2026-08-10 22:52 UTCVendor advisory
  39. 2026-08-10 22:52 UTCGHSA enrichment
  40. 2026-08-10 11:26 UTCVendor advisory
  41. 2026-08-10 11:26 UTCGHSA enrichment
  42. 2026-08-10 00:00 UTCEG score recompute
  43. 2026-08-10 00:00 UTCVendor advisory
  44. 2026-08-10 00:00 UTCGHSA enrichment
  45. 2026-08-09 13:47 UTCEPSS rescore
  46. 2026-08-09 12:35 UTCVendor advisory
  47. 2026-08-09 12:35 UTCGHSA enrichment
  48. 2026-08-09 01:09 UTCEG score recompute
  49. 2026-08-09 01:09 UTCVendor advisory
  50. 2026-08-09 01:09 UTCGHSA enrichment
  51. 2026-08-08 16:37 UTCEPSS rescore
  52. 2026-08-08 13:43 UTCVendor advisory
  53. 2026-08-08 13:43 UTCGHSA enrichment
  54. 2026-08-08 02:17 UTCEG score recompute
  55. 2026-08-08 02:17 UTCVendor advisory
  56. 2026-08-08 02:17 UTCGHSA enrichment
  57. 2026-08-07 14:51 UTCVendor advisory
  58. 2026-08-07 14:51 UTCGHSA enrichment
  59. 2026-08-07 03:25 UTCVendor advisory
  60. 2026-08-07 03:25 UTCGHSA enrichment
  61. 2026-08-06 15:59 UTCEG score recompute
  62. 2026-08-06 15:59 UTCVendor advisory
  63. 2026-08-06 15:59 UTCGHSA enrichment
  64. 2026-08-06 13:47 UTCEPSS rescore
  65. 2026-08-06 04:34 UTCEG score recompute
  66. 2026-08-06 04:34 UTCVendor advisory
  67. 2026-08-06 04:34 UTCGHSA enrichment
  68. 2026-08-05 19:17 UTCEPSS rescore
  69. 2026-08-05 19:17 UTCEPSS rescore
  70. 2026-08-05 17:08 UTCVendor advisory
  71. 2026-08-05 17:08 UTCGHSA enrichment
  72. 2026-08-05 05:42 UTCGHSA enrichment
  73. 2026-08-04 18:14 UTCEG score recompute
  74. 2026-08-04 18:14 UTCGHSA enrichment
  75. 2026-08-04 15:10 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-67322?
CVE-2026-67322 is a high vulnerability published on August 1, 2026. GitPython before 3.1.52 is vulnerable to environment-variable exfiltration in Repo.clonefrom(). The caller-supplied remote URL is passed through Git.polishurl(), which on non-Cygwin platforms calls os.path.expandvars() on the URL before invoking git clone. An attacker who controls the clone URL can…
When was CVE-2026-67322 disclosed?
CVE-2026-67322 was first published in the National Vulnerability Database on August 1, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67322 actively exploited?
CVE-2026-67322 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.4% of all scored CVEs.
What is the CVSS score of CVE-2026-67322?
CVE-2026-67322 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-67322?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67322, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-67322?

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

Start Free Scan →Browse All CVEs