# CVE-2026-50141: Woodpecker gRPC agent_id metadata can be spoofed- cross-tenant agent impersonation

> Authenticated agents can impersonate others by spoofing gRPC metadata, allowing cross-tenant agent impersonation in Woodpecker CI.

- **Severity:** High 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Jun 2026
- **Updated:** 18 Jun 2026
- **Also known as:** GHSA-g7mm-9vx7-jm7h, GO-2026-5976

## What is CVE-2026-50141?

CVE-2026-50141 is a high-severity authentication bypass vulnerability in woodpecker-ci woodpecker, published on 18 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2026-50141?

5 open source packages ship an affected version, including go.woodpecker-ci.org/woodpecker/v3, go.woodpecker-ci.org/woodpecker and go.woodpecker-ci.org/woodpecker/v2.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `go.woodpecker-ci.org/woodpecker/v3` | Go | From 3.0.0 | 3.14.1 |
| `go.woodpecker-ci.org/woodpecker/v3` | Go | From 3.0.0 | 3.14.1 |
| `go.woodpecker-ci.org/woodpecker/v3` | Go | From 3.0.0 | 3.14.1 |
| `go.woodpecker-ci.org/woodpecker` | Go | All versions | None |
| `go.woodpecker-ci.org/woodpecker/v2` | Go | All versions | None |

## How do I fix CVE-2026-50141?

Upgrade go.woodpecker-ci.org/woodpecker/v3 to 3.14.1 or later.

## Is CVE-2026-50141 being exploited?

There is no known exploitation of CVE-2026-50141 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50141 and fix it if it is affected.

What it is: CVE-2026-50141 is a high-severity authentication bypass vulnerability in woodpecker-ci woodpecker, published on 18 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-50141 in the wild and no public exploit code.

Affected packages and fixed versions:
- go.woodpecker-ci.org/woodpecker/v3 (Go): affected from 3.0.0; fixed in 3.14.1
- go.woodpecker-ci.org/woodpecker/v3 (Go): affected from 3.0.0; fixed in 3.14.1
- go.woodpecker-ci.org/woodpecker/v3 (Go): affected from 3.0.0; fixed in 3.14.1
- go.woodpecker-ci.org/woodpecker (Go): affected all versions; no fix listed
- go.woodpecker-ci.org/woodpecker/v2 (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-50141/ (Markdown: https://insights.sbomify.com/CVE-2026-50141/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50141
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50141
- OSV: https://osv.dev/vulnerability/CVE-2026-50141

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-50141/
Summaries are generated and may contain mistakes; the official description above is the record.