Summary
Woodpecker gRPC agent_id metadata can be spoofed- cross-tenant agent impersonation
Workarounds
Disable org agents (WOODPECKER_DISABLE_USER_AGENT_REGISTRATION=true) and delete existing ones
Resources
Public ref: https://github.com/woodpecker-ci/woodpecker/issues/6541
Private com: https://github.com/woodpecker-ci/woodpecker-security/issues/21
Impact
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Direct patch: https://github.com/woodpecker-ci/woodpecker/pull/6567
Later proper fix: https://github.com/woodpecker-ci/woodpecker/pull/6569
Frequently Asked Questions
- What is CVE-2026-50141? CVE-2026-50141 is a high-severity security vulnerability in go.woodpecker-ci.org/woodpecker/v3 (go), affecting versions >= 3.0.0, < 3.14.1. It is fixed in 3.14.1.
- Which versions of go.woodpecker-ci.org/woodpecker/v3 are affected by CVE-2026-50141? go.woodpecker-ci.org/woodpecker/v3 (go) versions >= 3.0.0, < 3.14.1 is affected.
- Is there a fix for CVE-2026-50141? Yes. CVE-2026-50141 is fixed in 3.14.1. Upgrade to this version or later.
- Is CVE-2026-50141 exploitable, and should I be worried? Whether CVE-2026-50141 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-50141 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-50141? Upgrade
go.woodpecker-ci.org/woodpecker/v3to 3.14.1 or later.