Insecure path traversal in Git Trigger Source can lead to arbitrary file readGHSA-qpgx-64h2-gc3c
HIGHFix: argoproj/argo-events#1965GHSA-qpgx-64h2-gc3c is a high-severity (CVSS 7.5) Path Traversal vulnerability in github.com/argoproj/argo-events. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for github.com/argoproj/argo-events — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/argoproj/argo-eventsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
A path traversal issue was found in the (g *GitArtifactReader).Read() API. Read() calls into (g *GitArtifactReader).readFromRepository() that opens and reads the file that contains the trigger resource definition:
func (g *GitArtifactReader) readFromRepository(r *git.Repository, dir string)
No checks are made on this file at read time, which could lead an attacker to read files anywhere on the system. This could be achieved by either using symbolic links, or putting ../ in the path.
Patches
A patch for this vulnerability has been released in the following Argo Events version:
v1.7.1
Credits
Disclosed by Ada Logics in a security audit sponsored by CNCF and facilitated by OSTIF.
For more information
Open an issue in the Argo Events issue tracker or discussions Join us on Slack in channel #argo-events
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/argoproj/argo-events | all versions | 1.7.1go get github.com/argoproj/argo-events@v1.7.1 |
Affected Products
argo eventsargo_events_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/argoproj/argo-events, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/argoproj/argo-events to 1.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qpgx-64h2-gc3c is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is GHSA-qpgx-64h2-gc3c in your dependencies?
Find it across Go, including transitive dependencies.