GHSA-gv2h-gf8m-r68j
HIGHExposure of server configuration in github.com/go-vela/server
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
github.com/go-vela/compilerReal-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
What kind of vulnerability is it? Who is impacted?
- The ability to expose configuration set in the Vela server via pipeline template functionality.
- It impacts all users of Vela.
Sample of template exposing server configuration using Sprig's env function:
metadata:
template: true
steps:
- name: sample
image: alpine:latest
commands:
# OAuth client ID for Vela <-> GitHub communication
- echo {{ env "VELA_SOURCE_CLIENT" }}
# secret used for server <-> worker communication
- echo {{ env "VELA_SECRET" }}
Patches
Has the problem been patched? What versions should users upgrade to?
- Upgrade to
0.6.1
Additional Recommended Action(s)
- Rotate all secrets
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
- No
For more information
If you have any questions or comments about this advisory:
- Email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/go-vela/compiler | all versions | 0.6.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/go-vela/compiler. 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/go-vela/compiler to 0.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gv2h-gf8m-r68j 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-gv2h-gf8m-r68j 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-gv2h-gf8m-r68j. 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-gv2h-gf8m-r68j in your dependencies?
O3 detects GHSA-gv2h-gf8m-r68j across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.