Missing Authorization Affecting go.woodpecker-ci.org/woodpecker/v3/pipeline/backend/kubernetes package, versions <3.16.0
Threat Intelligence
This vulnerability is trending on Twitter; this may indicate a growing threat.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Missing Authorization vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-GOLANG-GOWOODPECKERCIORGWOODPECKERV3PIPELINEBACKENDKUBERNETES-17972541
- published10 Aug 2026
- disclosed14 Jul 2026
- creditUnknown
Introduced: 14 Jul 2026
NewCVE-2026-61549 (opens in a new tab)How to fix?
Upgrade go.woodpecker-ci.org/woodpecker/v3/pipeline/backend/kubernetes to version 3.16.0 or higher.
Overview
Affected versions of this package are vulnerable to Missing Authorization via the serviceAccountName field in the Kubernetes backend configuration. An attacker can gain elevated privileges by specifying an arbitrary ServiceAccount, allowing access to sensitive resources and potential full cluster compromise. This is only exploitable if the Kubernetes backend is enabled and users have Push permissions on a connected repository.
Workaround
This vulnerability can be mitigated by restricting Push access to trusted users, hardening the pipeline namespace to avoid privileged ServiceAccounts, disabling ServiceAccount token automounting, enforcing admission policies to reject unexpected serviceAccountName values, or using dedicated isolated namespaces without sensitive RBAC bindings.