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: 0.9%CVSS: 8.8Exploit: None knownExposed services: Not assessed

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.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.9%
EPSS %ILE
58th
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 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(9)

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

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatansible-automation-platform-25/controller-rhel8:17896070212026-09-23redhat
redhatansible-automation-platform-26/controller-rhel9:17896737392026-09-23redhat
redhatansible-automation-platform-27/controller-rhel9:17895806842026-09-23redhat
redhatsatellite/iop-vmaas-rhel9:17896118582026-09-17redhat
redhatsatellite/iop-vmaas-rhel9:17896119982026-09-17redhat
redhatsatellite/iop-vulnerability-engine-rhel9:17896076052026-09-17redhat
redhatsatellite/iop-vulnerability-engine-rhel9:17896370822026-09-17redhat
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 rangeFix by version rangeDependents
python-git3.1.30-1 ... 3.1.62-2 (13 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-git3.1.44-1 ... 3.1.62-2 (7 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-1
  • every version up to 3.1.61-1: fixed in 3.1.61-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
gitpython0.1.7 ... 3.1.9 (110 versions)
  • every version up to 3.1.58: fixed in 3.1.58
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 109× 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 186 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

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 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 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76220?
CVE-2026-76220 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-76220?
A fix for CVE-2026-76220 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-76220 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs