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 51% 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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.8Exploit: NoneExposed: 0

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.8(medium)
EPSS
49.5%
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.
github Patch Available🟡 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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-git (2.1.8-1ubuntu0.1~esm4) @ bionic2026-06-28ubuntu

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

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
gitpython3.1.30 ... 3.1.46 (16 versions)3.1.47—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

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

Related CVEs(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 in the National Vulnerability Database 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 49.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42215, 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-42215

Explore →

Is Your Infrastructure Affected by CVE-2026-42215?

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

Start Free Scan →Browse All CVEs