CVE-2026-73619: External Control of File Name or Path in gitpython-developers GitPython
GitPython versions before 3.1.57 have a vulnerability where the denylist in the unsafe_git_archive_options guard is incomplete, omitting the --add-file and --add-virtual-file options. This allows attackers to supply these options to the Repo.archive() method to read arbitrary files from the filesystem and include them in the archive returned by the function.
AI Analysis
Technical Summary
CVE-2026-73619 affects GitPython prior to version 3.1.57. The vulnerability arises because the denylist protecting the unsafe_git_archive_options in the Repo.archive() method does not include the --add-file and --add-virtual-file options. An attacker with at least low privileges can exploit this by passing these options to read arbitrary files from the filesystem and include them in the archive output. The CVSS 4.0 score is 7.1, indicating a high severity vulnerability with network attack vector, low attack complexity, no privileges required beyond low, no user interaction, and high impact on confidentiality.
Potential Impact
An attacker can read arbitrary files on the filesystem by exploiting the incomplete denylist in the unsafe_git_archive_options guard. This can lead to unauthorized disclosure of sensitive information included in the archive generated by Repo.archive(). There is no indication of privilege escalation, integrity, or availability impact. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid using untrusted input with the Repo.archive() method or restrict usage to trusted users only.
CVE-2026-73619: External Control of File Name or Path in gitpython-developers GitPython
Description
GitPython versions before 3.1.57 have a vulnerability where the denylist in the unsafe_git_archive_options guard is incomplete, omitting the --add-file and --add-virtual-file options. This allows attackers to supply these options to the Repo.archive() method to read arbitrary files from the filesystem and include them in the archive returned by the function.
CVSS v4.0
Score 7.1high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-73619 affects GitPython prior to version 3.1.57. The vulnerability arises because the denylist protecting the unsafe_git_archive_options in the Repo.archive() method does not include the --add-file and --add-virtual-file options. An attacker with at least low privileges can exploit this by passing these options to read arbitrary files from the filesystem and include them in the archive output. The CVSS 4.0 score is 7.1, indicating a high severity vulnerability with network attack vector, low attack complexity, no privileges required beyond low, no user interaction, and high impact on confidentiality.
Potential Impact
An attacker can read arbitrary files on the filesystem by exploiting the incomplete denylist in the unsafe_git_archive_options guard. This can lead to unauthorized disclosure of sensitive information included in the archive generated by Repo.archive(). There is no indication of privilege escalation, integrity, or availability impact. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid using untrusted input with the Repo.archive() method or restrict usage to trusted users only.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-13T11:16:27.835Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7dbdfbbf8831d5393225ed
Added to database: 08/13/2026, 12:52:11 UTC
Last enriched: 08/13/2026, 12:56:15 UTC
Last updated: 08/13/2026, 18:14:36 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.