CVE-2026-76220

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-19. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

GitPython before 3.1.58 contains a command execution vulnerability in the check_unsafe_options guard that can be bypassed by combining a single-character kwarg with split_single_char_options=False. Attackers can supply a crafted kwargs dictionary to guarded methods like clone_from to emit a joined token parsed as --upload-pack, enabling arbitrary OS command execution at default allow_unsafe_options=False.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

August 19, 2026

Last Modified

September 3, 2026

Advisory Details (2)

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

GitPython before 3.1.58 Command Execution via split_single_char_options | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitpython-before-command-execution-via-split-single-char-options
github Patch Available🟡 PoC Available

Unsafe git option guard bypass via split_single_char_options=False short-option token smuggling enables command execution · Advisory · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-wvpp-8hx9-p66j

Vendor Advisories for CVE-2026-76220(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpython3.12-gitpython-0:3.1.59-1.el9pc2026-09-03redhat

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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.30-1 ... 3.1.61-1 (11 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-1, 3.1.61-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-13.1.61-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
gitpython0.1.7 ... 3.1.9 (110 versions)3.1.58—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 123× 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 132 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-76220?
CVE-2026-76220 is a high vulnerability published on August 19, 2026. GitPython before 3.1.58 contains a command execution vulnerability in the checkunsafeoptions guard that can be bypassed by combining a single-character kwarg with splitsinglecharoptions=False. Attackers can supply a crafted kwargs dictionary to guarded methods like clonefrom to emit a joined token…
When was CVE-2026-76220 disclosed?
CVE-2026-76220 was first published in the National Vulnerability Database on August 19, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-76220 actively exploited?
CVE-2026-76220 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.1% of all scored CVEs.
What is the CVSS score of CVE-2026-76220?
CVE-2026-76220 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-76220?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76220, 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-76220

Explore →

Is Your Infrastructure Affected by CVE-2026-76220?

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

Start Free Scan →Browse All CVEs