Vela Server Has Insufficient Webhook Payload Data Verification

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.5 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

EPSS

• CVE-2025-27616: 0.27% estimated exploitation activity in the next 30 days; percentile 18.57 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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. 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. Patches v0.26.3 — Image: target/vela-server:v0.26.3 v0.25.3 — Image: target/vela-server:v0.25.3 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.

Published by the source

10 Mar 2025, 22:24 UTC

Last modified by the source

14 Mar 2025, 20:02 UTC

Source last checked

26 Oct 2026, 15:09 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9m63-33q3-xq5x

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-27616

Advisory: Vela Server Has Insufficient Webhook Payload Data Verification
IDs: CVE-2025-27616, GHSA-9m63-33q3-xq5x
Record: https://patchnext.com/advisories/cve-2025-27616 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/go-vela/server 0.26.3, 0.25.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/go-vela/server: affected < 0.25.3; >= 0.26.0, <= 0.26.2; fixed in 0.25.3, 0.26.3

## Suggested inspection (read-only)
- Go github.com/go-vela/server: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/go-vela/server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9m63-33q3-xq5x (GitHub-reviewed advisory GHSA-9m63-33q3-xq5x lists affected ranges: Go github.com/go-vela/server >=0 =0.26.0 <=0.26.2)

Commands are suggestions: review each one before running it.