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.
CVE-2026-50141
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EG Risk
- 37(Track)EG Risk 37/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 15.9%
- KEV
- Not listed
Published
June 18, 2026
Last Modified
June 23, 2026
Advisory Details (4)
Auto-updated Jun 18, 2026gRPC agent_id metadata can be spoofed- cross-tenant agent impersonation · Advisory · woodpecker-ci/woodpecker · GitHub
https://github.com/woodpecker-ci/woodpecker/security/advisories/GHSA-g7mm-9vx7-jm7hserver: for grpc store extracted agentID in context
Fix merged in woodpecker-ci/woodpecker PR #6569 on 2026-05-12 — awaiting tagged release
https://github.com/woodpecker-ci/woodpecker/pull/6569Server: make sure agent_id can not be spoofed by agent
Fix merged in woodpecker-ci/woodpecker PR #6567 on 2026-05-12 — awaiting tagged release
https://github.com/woodpecker-ci/woodpecker/pull/6567gRPC agent_id metadata can be spoofed- cross-tenant agent impersonation · Issue #6541 · woodpecker-ci/woodpecker · GitHub
https://github.com/woodpecker-ci/woodpecker/issues/6541Vendor Advisories for CVE-2026-50141(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(3 across 1 ecosystem)
Go(3)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| go.woodpecker-ci.org/woodpecker | — | — | — |
| go.woodpecker-ci.org/woodpecker/v2 | — | — | — |
| go.woodpecker-ci.org/woodpecker/v3 | — | 3.14.1 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 40× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:18 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
Show 17 moreShow fewer
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-18 15:54 UTCEG score recompute
- 2026-06-18 15:53 UTCNVD updatefirst tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-290 · CWE-639
- CVE-2018-25318EG 9.8CRITICAL
- CVE-2018-25317EG 9.8CRITICAL
- CVE-2018-25316EG 9.8CRITICAL
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2018-5353EG 9.8EPSS 95%CRITICAL
- CVE-2019-15310EG 9.8EPSS 94%CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16871EG 9.8EPSS 92%CRITICAL
- CVE-2019-18259EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-50141?
When was CVE-2026-50141 disclosed?
Is CVE-2026-50141 actively exploited?
What is the CVSS score of CVE-2026-50141?
How do I remediate CVE-2026-50141?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50141
Is Your Infrastructure Affected by CVE-2026-50141?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.