go.woodpecker-ci.org/woodpecker/v3
Affected
- introduced
0, fixed3.16.0(semver)
Fixed versions
3.16.0
Fix
- Fixed version
3.16.0go get go.woodpecker-ci.org/woodpecker/[email protected]
Advisory
Also known as: CVE-2026-61549, GO-2026-5992
Woodpecker: Privilege escalation via unrestricted serviceAccountName in the Kubernetes backend
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:
default ServiceAccount minimally privileged.serviceAccountName.Resources
609ba481b5e912f59aaae8ca7bc22b44523c5e37v1.0.0 through v3.15.0pipeline/backend/kubernetes/backend_options.go (field ServiceAccountName), pipeline/backend/kubernetes/pod.go (assigned to pod spec with no gating)High Basis: The source's own band: HIGH
0, fixed 3.16.0 (semver)3.16.0
3.16.0go get go.woodpecker-ci.org/woodpecker/[email protected]1.0.0, last affected 1.0.4 (semver)None listed
No fixed version is listed.
0, last affected 2.8.3 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0