Vulnerability in go.woodpecker-ci.org/woodpecker/v3 (CVE-2026-50141)
Summary
Vulnerability in go.woodpecker-ci.org/woodpecker/v3 (CVE-2026-50141). Risk of unauthorized operations or information disclosure. Exploitable via agent_id. Mitigation: upgrade to 3.14.1 or later.
Original description
The description as published by the source.
Woodpecker is a CI/CD engine. Starting in version 3.0.0 and prior to version 3.14.1, a vulnerability in Woodpecker CI's gRPC layer allowed any authenticated agent to impersonate any other agent on the same server by injecting a forged agent_id value into outgoing gRPC metadata. The server correctly verified the JWT token but then discarded the verified agent identity in favor of the client-supplied value. Version 3.14.1 patches the issue. As a workaround, disable org agents (WOODPECKER_DISABLE_USER_AGENT_REGISTRATION=true) and delete existing ones.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-50141 has been found in go.woodpecker-ci.org/woodpecker/v3.
Attackers can target a specific entry point like agent_id over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade go.woodpecker-ci.org/woodpecker/v3 to 3.14.1 or later.
If unsure, ask your IT team or search "go.woodpecker-ci.org/woodpecker/v3 CVE-2026-50141" on the vendor's site.
CVE-2026-50141 (go.woodpecker-ci.org/woodpecker/v3) — CWE-290
Attack surface: agent_id
Patched: 3.14.1 — apply immediately
Workaround: Disable org agents (WOODPECKER_DISABLE_USER_AGENT_REGISTRATION=true) and delete existing ones
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-290) exists in go.woodpecker-ci.org/woodpecker/v3. Attackers reach the vulnerable code path via agent_id.
Check the vendor advisory for the affected versions of go.woodpecker-ci.org/woodpecker/v3. Attack surface: agent_id.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.14.1.
Workaround: Disable org agents (WOODPECKER_DISABLE_USER_AGENT_REGISTRATION=true) and delete existing ones
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'go.woodpecker-ci.org/woodpecker/v3' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'go.woodpecker-ci.org/woodpecker/v3' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
go.woodpecker-ci.org/woodpecker/v3を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Disable org agents (`WOODPECKER_DISABLE_USER_AGENT_REGISTRATION=true`) and delete existing onesパッチが適用されるまでの応急処置として、Disable org agents (
WOODPECKER_DISABLE_USER_AGENT_REGISTRATION=true) and delete existing ones を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade go.woodpecker-ci.org/woodpecker/v3 to 3.14.1ステージング環境で 3.14.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- report github.com
- report github.com
- web github.com