Em resumo
- CVE-2026-61549 é uma vulnerabilidade CRÍTICO (CVSS 9.0) que afeta github.com/woodpecker-ci/woodpecker, go.woodpecker-ci.org/woodpecker, go.woodpecker-ci.org/woodpecker/v2.
- Chance de exploração nos próximos 30 dias (EPSS): 0.28%, maior que 20.3% das vulnerabilidades.
- Correção: atualize para 3.16.0 ou posterior.
Description
Impact
A privilege escalation vulnerability affects Woodpecker instances using the Kubernetes backend.
The pipeline option backend_options.kubernetes.serviceAccountName was passed directly to the pod spec without any admin gating.
Who is impacted: any operator running the Kubernetes backend. Any user with Push permission on a connected repository can run pipeline pods under an arbitrary ServiceAccount in the pipeline namespace, gaining that account's RBAC permissions. If a privileged ServiceAccount is reachable in that namespace, this can lead to secret exfiltration (database credentials, API keys, TLS certs) and full cluster takeover.
Patches
https://github.com/woodpecker-ci/woodpecker/pull/6792
Workarounds
Operators who cannot upgrade immediately can mitigate by any of:
- Restrict Push access on repositories connected to the Kubernetes-backed instance to
trusted users only.
- Harden the pipeline namespace: ensure no privileged ServiceAccount exists or is bound in
the namespace where pipeline pods run; keep the
default ServiceAccount minimally privileged.
- Disable ServiceAccount token automounting for ServiceAccounts that should not be used by
pipelines.
- Enforce an admission policy (e.g. OPA/Gatekeeper, Kyverno, or a ValidatingAdmissionPolicy)
that rejects pipeline pods setting an unexpected
serviceAccountName.
- Use a dedicated, isolated namespace per org/instance with no sensitive RBAC bindings.
Resources
- Vulnerable option introduced in commit
609ba481b5e912f59aaae8ca7bc22b44523c5e37
- Affected versions:
v1.0.0 through v3.15.0
- Source:
pipeline/backend/kubernetes/backend_options.go (field ServiceAccountName),
pipeline/backend/kubernetes/pod.go (assigned to pod spec with no gating)
NVD description
Woodpecker is a CI/CD engine. From 1.0.0 until 3.16.0, pipeline/backend/kubernetes/backend_options.go defines backend_options.kubernetes.serviceAccountName, and the Kubernetes backend in pipeline/backend/kubernetes/pod.go copies that pipeline-step value directly into the pod specification without administrator authorization. Any user with Push permission on a connected repository can therefore run pipeline pods under an arbitrary ServiceAccount in the pipeline namespace and inherit that account's RBAC permissions. When a privileged ServiceAccount is reachable, the attacker can exfiltrate secrets such as database credentials, API keys, and TLS certificates and may take over the cluster. This issue is fixed in version 3.16.0.
Mais vulnerabilidades de github.com/woodpecker-ci/woodpecker
Ver tudo →Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free