GHSA-qpgx-64h2-gc3c is a high-severity (CVSS 7.5) Path Traversal vulnerability in github.com/argoproj/argo-events. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-qpgx-64h2-gc3c is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Insecure path traversal in Git Trigger Source can lead to arbitrary file read
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.1 |
Research 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-qpgx-64h2-gc3c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-qpgx-64h2-gc3c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-qpgx-64h2-gc3c in your dependencies?
O3 detects GHSA-qpgx-64h2-gc3c across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.