CVE-2026-73619

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

GitPython before 3.1.57 contains an incomplete denylist in the unsafe_git_archive_options guard that omits --add-file and --add-virtual-file options. Attackers can supply these options to Repo.archive() to read arbitrary files from the filesystem and include them in the returned archive.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
45(Track)
EG Risk 45/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
Severity65% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 15, 2026

Advisory Details (2)

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

GitPython before 3.1.57 Arbitrary File Read via Repo.archive() | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitpython-before-arbitrary-file-read-via-repo-archive
github Patch Available🟡 PoC Available

Incomplete unsafe_git_archive_options denylist omits --add-file / --add-virtual-file, enabling arbitrary file read via Repo.archive() · Advisory · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-539m-9xh6-q6rr

Vendor Advisories for CVE-2026-73619(1)

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
gitpython0.1.7 ... 3.1.9 (109 versions)3.1.57

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 28× 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.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 16:29 UTCGHSA enrichment
  3. 2026-08-19 18:31 UTCEG score recompute
  4. 2026-08-19 18:31 UTCGHSA enrichment
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-18 20:15 UTCGHSA enrichment
  7. 2026-08-17 22:14 UTCEG score recompute
  8. 2026-08-17 22:14 UTCGHSA enrichment
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-17 00:16 UTCEG score recompute
  11. 2026-08-17 00:16 UTCGHSA enrichment
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 02:18 UTCEG score recompute
  15. 2026-08-16 02:18 UTCGHSA enrichment
  16. 2026-08-16 02:15 UTCEPSS rescore
  17. 2026-08-15 04:20 UTCEG score recompute
  18. 2026-08-15 04:20 UTCGHSA enrichment
  19. 2026-08-15 03:23 UTCEG score recompute
  20. 2026-08-15 03:23 UTCGHSA enrichment
  21. 2026-08-15 01:31 UTCEPSS rescore
  22. 2026-08-14 17:08 UTCEG score recompute
  23. 2026-08-14 17:08 UTCGHSA enrichment
  24. 2026-08-14 10:31 UTCGHSA enrichment
  25. 2026-08-13 12:33 UTCEG score recompute
Show 3 more
  1. 2026-08-13 12:33 UTCGHSA enrichment
  2. 2026-08-13 11:42 UTCEG score recompute
  3. 2026-08-13 11:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-73619?
CVE-2026-73619 is a medium vulnerability published on August 13, 2026. GitPython before 3.1.57 contains an incomplete denylist in the unsafegitarchive_options guard that omits --add-file and --add-virtual-file options. Attackers can supply these options to Repo.archive() to read arbitrary files from the filesystem and include them in the returned archive.
When was CVE-2026-73619 disclosed?
CVE-2026-73619 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73619 actively exploited?
CVE-2026-73619 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 86.3% of all scored CVEs.
What is the CVSS score of CVE-2026-73619?
CVE-2026-73619 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-73619?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73619, 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-73619

Explore →

Is Your Infrastructure Affected by CVE-2026-73619?

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