High (8.5) in go-vela server. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/go-vela/server 0.25.3, 0.26.3.
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.
Severity
CVSS 3.1
8.5 high
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.3%(unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 19th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-03-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-290Authentication Bypass by Spoofing CWE-345Insufficient Verification of Data Authenticity
Show the promptExplain CVE-2025-27616 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-27616?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-27616?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-27616 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.
Attack patterns (CAPEC)
CAPEC-21 Exploitation of Trusted Identifiers Likelihood: High · Severity: High
CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High
CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
CAPEC-461 Web Services API Signature Forgery Leveraging Hash Function Extension Weakness Severity: High