CVE-2026-50141: woodpecker · Authentication Bypass by Spoofing
Affects woodpeckerSource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 3.14.1 soon.
Data as of 31 Oct 2026, 20:20 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.14.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:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.
What to do
Upgrade woodpecker to 3.14.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| woodpecker-ciwoodpecker | Affected
| Fixed in
|
GitHubwoodpecker-ci/woodpeckerpkg:github/woodpecker-ci/woodpeckerOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Woodpecker CI to version 3.14.1 or later to apply the official fix. As a temporary workaround, disable organization agents by setting the environment variable WOODPECKER_DISABLE_USER_AGENT_REGISTRATION=true and delete any existing organization agents. This reduces the risk until the patch can be applied.
Description
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.
References
- github.com/woodpecker-ci/woodpecker/security/advisories/GHSA-g7mm-9vx7-jm7h (opens in a new tab)
- github.com/woodpecker-ci/woodpecker-security/issues/21 (opens in a new tab)
- github.com/woodpecker-ci/woodpecker/issues/6541 (opens in a new tab)
- github.com/woodpecker-ci/woodpecker/pull/6567 (opens in a new tab)
- github.com/woodpecker-ci/woodpecker/pull/6569 (opens in a new tab)