Vela Server has Insufficient Webhook Payload Data Verification
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| go-vela | server | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Go-vela | Server | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-7802 | Vela Server Has Insufficient Webhook Payload Data Verification |
Github GHSA |
GHSA-9m63-33q3-xq5x | Vela Server Has Insufficient Webhook Payload Data Verification |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.266% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Vela is a Pipeline Automation (CI/CD) framework built on Linux container technology written in Golang. Prior to versions 0.25.3 and 0.26.3, by spoofing a webhook payload with a specific set of headers and body data, an attacker could transfer ownership of a repository and its repo level secrets to a separate repository. These secrets could be exfiltrated by follow up builds to the repository. Users with an enabled repository with access to repo level CI secrets in Vela are vulnerable to the exploit, and any user with access to the CI instance and the linked source control manager can perform the exploit. Versions 0.25.3 and 0.26.3 fix the issue. No known workarounds are available. | |
| Title | Vela Server has Insufficient Webhook Payload Data Verification | |
| Weaknesses | CWE-290 CWE-345 |
|
| References |
|
|
| Metrics |
cvssV3_1
|