CVE-2026-42215

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 48% of all CVEs by exploit prediction. 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, nvd
Elevated
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: Elevated riskExposed services: Not assessed

A fix is available — apply it.

GitPython is a python library used to interact with Git repositories. From version 3.1.30 to before version 3.1.47, GitPython blocks dangerous Git options such as --upload-pack and --receive-pack by default, but the equivalent Python kwargs upload_pack and receive_pack bypass that check. If an application passes attacker-controlled kwargs into Repo.clone_from(), Remote.fetch(), Remote.pull(), or Remote.push(), this leads to arbitrary command execution even when allow_unsafe_options is left at its default value of False. This issue has been patched in version 3.1.47.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/100

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%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.9%
EPSS %ILE
58th
KEV
Not listed

Published

May 7, 2026

Last Modified

May 11, 2026

Advisory Details (2)

Auto-updated May 7, 2026
🔬 Proof of concept available. Patch available. Sources: github.
githubMentions a patch (unverified)🟡 PoC Available

Command injection via Git options bypass · Advisory · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-rpm5-65cw-6hj4
generic

Release 3.1.47 - with security fixes · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/releases/tag/3.1.47

Vendor Advisories for CVE-2026-42215(17)

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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-git (1.0.1+git137-gc8b8379-2.1ubuntu0.1~esm4) @ xenial2026-08-23ubuntu
redhatpython3.12-gitpython-0:3.1.50-1.el9ap2026-07-20redhat
redhatansible-automation-platform-26/hub-rhel9:17839795932026-07-20redhat

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 rangeFix by version rangeDependents
python-git3.1.14-1 ... 3.1.50-1 (14 versions)
  • every version on: no fix on record
—
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
  • every version up to 3.1.50-1: fixed in 3.1.50-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
gitpython3.1.30 ... 3.1.46 (16 versions)
  • 3.1.30 up to 3.1.47: fixed in 3.1.47
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

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

Frequently asked(5)

What is CVE-2026-42215?
CVE-2026-42215 is a high vulnerability published on May 7, 2026. GitPython is a python library used to interact with Git repositories. From version 3.1.30 to before version 3.1.47, GitPython blocks dangerous Git options such as --upload-pack and --receive-pack by default, but the equivalent Python kwargs uploadpack and receivepack bypass that check. If an…
When was CVE-2026-42215 disclosed?
CVE-2026-42215 was first published on May 7, 2026, with the most recent update on May 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42215 actively exploited?
CVE-2026-42215 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-42215?
CVE-2026-42215 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-42215?
A fix for CVE-2026-42215 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-42215 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-42215

Explore →

Is Your Infrastructure Affected by CVE-2026-42215?

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

Book a Demo →Browse All CVEs