CVE-2025-27616

Vela Server Has Insufficient Webhook Payload Data Verification

Method

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.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

There are no workarounds to the issue.

References

Are there any links users can visit to find out more?

Please see linked CWEs (common weakness enumerators) for more information.

Users with an enabled repository with access to repo level CI secrets in Vela are vulnerable to the exploit.

Any user with access to the CI instance and the linked source control manager can perform the exploit.

CVE-2025-27616 has a CVSS score of 8.5 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.25.3, 0.26.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

v0.26.3, Image: target/vela-server:v0.26.3
v0.25.3, Image: target/vela-server:v0.25.3

1. What is CVE-2025-27616? CVE-2025-27616 is a high-severity security vulnerability in github.com/go-vela/server (go), affecting versions < 0.25.3. It is fixed in 0.25.3, 0.26.3.
2. How severe is CVE-2025-27616? CVE-2025-27616 has a CVSS score of 8.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/go-vela/server are affected by CVE-2025-27616? github.com/go-vela/server (go) versions < 0.25.3 is affected.
4. Is there a fix for CVE-2025-27616? Yes. CVE-2025-27616 is fixed in 0.25.3, 0.26.3. Upgrade to this version or later.
5. Is CVE-2025-27616 exploitable, and should I be worried? Whether CVE-2025-27616 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-27616 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-27616?
   • Upgrade github.com/go-vela/server to 0.25.3 or later
   • Upgrade github.com/go-vela/server to 0.26.3 or later

Other vulnerabilities in github.com/go-vela/server