CVE-2026-42284

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 57% 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.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.1Exploit: NoneExposed: 0

A fix is available — apply it.

GitPython is a python library used to interact with Git repositories. Prior to version 3.1.47, _clone() validates multi_options as the original list, then executes shlex.split(" ".join(multi_options)). A string like "--branch main --config core.hooksPath=/x" passes validation (starts with --branch), but after split becomes ["--branch", "main", "--config", "core.hooksPath=/x"]. Git applies the config and executes attacker hooks during clone. This issue has been patched in version 3.1.47.

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
43.2%
KEV
Not listed

Published

May 7, 2026

Last Modified

May 8, 2026

Advisory Details (2)

Auto-updated May 7, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Unsafe option check validates multi_options before shlex.split transforms it · Advisory · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-x2qx-6953-8485
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 (1.0.1+git137-gc8b8379-2.1ubuntu0.1~esm4) @ xenial2026-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
gitpython0.1.7 ... 3.1.9 (99 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 / 49× 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 130 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-29 14:06 UTCEPSS rescore
  14. 2026-06-28 14:07 UTCEPSS rescore
  15. 2026-06-28 09:10 UTCEG score recompute
  16. 2026-06-28 09:10 UTCVendor advisory
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-27 14:22 UTCEG score recompute
  19. 2026-06-27 14:22 UTCVendor advisory
  20. 2026-06-27 03:08 UTCEPSS rescore
  21. 2026-06-26 22:13 UTCEG score recompute
  22. 2026-06-26 22:13 UTCVendor advisory
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-24 14:05 UTCEPSS rescore
Show 75 more
  1. 2026-06-23 21:33 UTCEPSS rescore
  2. 2026-06-22 14:25 UTCEPSS rescore
  3. 2026-06-22 14:25 UTCEPSS rescore
  4. 2026-06-21 14:56 UTCEPSS rescore
  5. 2026-06-21 14:56 UTCEPSS rescore
  6. 2026-06-21 01:59 UTCEPSS rescore
  7. 2026-06-19 19:25 UTCEPSS rescore
  8. 2026-06-18 17:52 UTCEPSS rescore
  9. 2026-06-18 17:52 UTCEPSS rescore
  10. 2026-06-17 17:53 UTCEPSS rescore
  11. 2026-06-17 03:35 UTCEG score recompute
  12. 2026-06-17 03:35 UTCVendor advisory
  13. 2026-06-16 17:52 UTCEPSS rescore
  14. 2026-06-15 17:49 UTCEPSS rescore
  15. 2026-06-15 03:59 UTCEG score recompute
  16. 2026-06-15 03:59 UTCVendor advisory
  17. 2026-06-14 15:50 UTCEG score recompute
  18. 2026-06-14 15:50 UTCVendor advisory
  19. 2026-06-14 03:33 UTCEG score recompute
  20. 2026-06-13 23:00 UTCEPSS rescore
  21. 2026-06-12 23:12 UTCEPSS rescore
  22. 2026-06-12 23:12 UTCEPSS rescore
  23. 2026-06-12 21:30 UTCEG score recompute
  24. 2026-06-12 21:30 UTCVendor advisory
  25. 2026-06-12 01:12 UTCEG score recompute
  26. 2026-06-12 01:12 UTCVendor advisory
  27. 2026-06-11 14:00 UTCEPSS rescore
  28. 2026-06-11 13:02 UTCEG score recompute
  29. 2026-06-11 13:02 UTCVendor advisory
  30. 2026-06-11 00:52 UTCEG score recompute
  31. 2026-06-11 00:52 UTCVendor advisory
  32. 2026-06-10 22:18 UTCEPSS rescore
  33. 2026-06-10 13:22 UTCEPSS rescore
  34. 2026-06-10 13:22 UTCEPSS rescore
  35. 2026-06-10 12:22 UTCEG score recompute
  36. 2026-06-10 12:22 UTCVendor advisory
  37. 2026-06-10 00:13 UTCEG score recompute
  38. 2026-06-10 00:13 UTCVendor advisory
  39. 2026-06-09 12:04 UTCEG score recompute
  40. 2026-06-09 12:04 UTCVendor advisory
  41. 2026-06-08 23:54 UTCEG score recompute
  42. 2026-06-08 23:54 UTCVendor advisory
  43. 2026-06-08 14:17 UTCEPSS rescore
  44. 2026-06-08 14:17 UTCEPSS rescore
  45. 2026-06-08 11:44 UTCEG score recompute
  46. 2026-06-08 11:44 UTCVendor advisory
  47. 2026-06-07 23:35 UTCEG score recompute
  48. 2026-06-07 23:35 UTCVendor advisory
  49. 2026-06-07 15:25 UTCEPSS rescore
  50. 2026-06-07 15:25 UTCEPSS rescore
  51. 2026-06-07 11:25 UTCEG score recompute
  52. 2026-06-07 11:25 UTCVendor advisory
  53. 2026-06-06 23:16 UTCEG score recompute
  54. 2026-06-06 23:16 UTCVendor advisory
  55. 2026-06-06 13:47 UTCEPSS rescore
  56. 2026-06-06 13:47 UTCEPSS rescore
  57. 2026-06-06 11:07 UTCEG score recompute
  58. 2026-06-06 11:07 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 10:20 UTCEG score recompute
  63. 2026-06-05 10:20 UTCVendor advisory
  64. 2026-06-05 06:10 UTCEPSS rescore
  65. 2026-06-05 06:10 UTCEPSS rescore
  66. 2026-06-04 22:11 UTCEG score recompute
  67. 2026-06-04 22:11 UTCVendor advisory
  68. 2026-06-04 13:12 UTCEPSS rescore
  69. 2026-06-04 13:12 UTCEPSS rescore
  70. 2026-06-04 10:01 UTCEG score recompute
  71. 2026-06-04 10:01 UTCVendor advisory
  72. 2026-06-03 21:50 UTCEG score recompute
  73. 2026-06-03 21:50 UTCVendor advisory
  74. 2026-06-03 09:40 UTCEG score recompute
  75. 2026-06-03 09:40 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-42284?
CVE-2026-42284 is a high vulnerability published on May 7, 2026. GitPython is a python library used to interact with Git repositories. Prior to version 3.1.47, clone() validates multioptions as the original list, then executes shlex.split(" ".join(multi_options)). A string like "--branch main --config core.hooksPath=/x" passes validation (starts with --branch),…
When was CVE-2026-42284 disclosed?
CVE-2026-42284 was first published in the National Vulnerability Database on May 7, 2026, with the most recent update on May 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42284 actively exploited?
CVE-2026-42284 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 43.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42284?
CVE-2026-42284 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-42284?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42284, 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-42284

Explore →

Is Your Infrastructure Affected by CVE-2026-42284?

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