Woodpecker gRPC agent_id metadata can be spoofed- cross-tenant agent impersonation
CVE-2026-50141GHSA-g7mm-9vx7-jm7h
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (go.woodpecker-ci.org/woodpecker/v3 3.14.1), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go go.woodpecker-ci.org/woodpecker/v3
- Affected
- >= 3.0.0, < 3.14.1
- Fixed in
- 3.14.1
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-g7mm-9vx7-jm7h lists affected ranges: Go go.woodpecker-ci.org/woodpecker/v3 >=3.0.0 <3.14.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2026-50141: 0.43% estimated exploitation activity in the next 30 days; percentile 37.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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 agentid 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. Patches Direct patch: https://github.com/woodpecker-ci/woodpecker/pull/6567 Later proper fix: https://github.com/woodpecker-ci/woodpecker/pull/6569 Workarounds Disable org agents (WOODPECKERDISABLEUSERAGENTREGISTRATION=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
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-g7mm-9vx7-jm7h
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-50141 Advisory: Woodpecker gRPC agent_id metadata can be spoofed- cross-tenant agent impersonation IDs: CVE-2026-50141, GHSA-g7mm-9vx7-jm7h Record: https://patchnext.com/advisories/cve-2026-50141 (revision 1, source checked 26 Oct 2026, 15:24 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.1) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: go.woodpecker-ci.org/woodpecker/v3 3.14.1. A vendor fix does not mean a deployment is fixed. ## Affected components - Go go.woodpecker-ci.org/woodpecker/v3: affected >= 3.0.0, < 3.14.1; fixed in 3.14.1 ## Suggested inspection (read-only) - Go go.woodpecker-ci.org/woodpecker/v3: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on go.woodpecker-ci.org/woodpecker/v3. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-g7mm-9vx7-jm7h (GitHub-reviewed advisory GHSA-g7mm-9vx7-jm7h lists affected ranges: Go go.woodpecker-ci.org/woodpecker/v3 >=3.0.0 <3.14.1) Commands are suggestions: review each one before running it.
Loading voting…