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)
- EPSS
- 15.8%
- 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/6541Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 24× in last 7d / 74× 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-12 05:46 UTCEPSS rescore
- 2026-07-12 02:19 UTCEG score recompute
- 2026-07-11 15:00 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 03:40 UTCEG score recompute
- 2026-07-10 16:20 UTCEG score recompute
- 2026-07-10 04:48 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 17:27 UTCEG score recompute
- 2026-07-09 06:02 UTCEG score recompute
- 2026-07-08 18:39 UTCEG score recompute
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 07:20 UTCEG score recompute
- 2026-07-07 19:53 UTCEG score recompute
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 03:18 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 15:59 UTCEG score recompute
- 2026-07-06 04:39 UTCEG score recompute
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 17:12 UTCEG score recompute
- 2026-07-05 05:51 UTCEG score recompute
Show 49 moreShow fewer
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 17:41 UTCEG score recompute
- 2026-07-04 06:19 UTCEG score recompute
- 2026-07-03 18:57 UTCEG score recompute
- 2026-07-03 07:38 UTCEG score recompute
- 2026-07-02 20:18 UTCEG score recompute
- 2026-07-02 09:00 UTCEG score recompute
- 2026-07-01 21:40 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 10:21 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 23:01 UTCEG score recompute
- 2026-06-30 11:42 UTCEG score recompute
- 2026-06-30 00:09 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 12:49 UTCEG score recompute
- 2026-06-29 01:30 UTCEG score recompute
- 2026-06-28 14:11 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 02:52 UTCEG score recompute
- 2026-06-27 15:33 UTCEG score recompute
- 2026-06-27 04:13 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 16:54 UTCEG score recompute
- 2026-06-26 05:35 UTCEG score recompute
- 2026-06-25 18:16 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 06:57 UTCEG score recompute
- 2026-06-24 19:34 UTCEG score recompute
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-24 08:14 UTCEG score recompute
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 20:53 UTCEG score recompute
- 2026-06-23 09:33 UTCEG score recompute
- 2026-06-22 22:13 UTCEG score recompute
- 2026-06-22 10:53 UTCEG score recompute
- 2026-06-21 23:30 UTCEG score recompute
- 2026-06-21 12:10 UTCEG score recompute
- 2026-06-21 00:41 UTCEG score recompute
- 2026-06-20 13:21 UTCEG score recompute
- 2026-06-20 02:02 UTCEG score recompute
- 2026-06-19 14:35 UTCEG score recompute
- 2026-06-19 03:15 UTCEG score recompute
- 2026-06-18 15:54 UTCEG score recompute
- 2026-06-18 15:53 UTCNVD updatefirst tracked
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
Explore the affected products and dependency analysis for 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.