How severe is GHSA-g7mm-9vx7-jm7h?

No CVSS score has been assigned to GHSA-g7mm-9vx7-jm7h yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g7mm-9vx7-jm7h?

GHSA-g7mm-9vx7-jm7h affects the following packages: go.woodpecker-ci.org/woodpecker/v3 (Go). Ecosystems affected: Go.

How do I fix GHSA-g7mm-9vx7-jm7h?

Update go.woodpecker-ci.org/woodpecker/v3 to 3.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g7mm-9vx7-jm7h is resolved across your whole dependency graph.

How do I detect GHSA-g7mm-9vx7-jm7h in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for go.woodpecker-ci.org/woodpecker/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-g7mm-9vx7-jm7h if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-g7mm-9vx7-jm7h actively exploited in the wild?

No public exploit code has been indexed for GHSA-g7mm-9vx7-jm7h yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-g7mm-9vx7-jm7h?

GHSA-g7mm-9vx7-jm7h has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 35th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-g7mm-9vx7-jm7h?

GHSA-g7mm-9vx7-jm7h is classified as CWE-290 (CWE-290), CWE-639 (CWE-639). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-g7mm-9vx7-jm7h published, and has it been updated?

GHSA-g7mm-9vx7-jm7h was published on July 14, 2026 and was last updated on July 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-g7mm-9vx7-jm7h — v3

Fix: woodpecker-ci/woodpecker#6567

GHSA-g7mm-9vx7-jm7h is a CWE-290 vulnerability in go.woodpecker-ci.org/woodpecker/v3. A fix is available for go.woodpecker-ci.org/woodpecker/v3 — see the affected versions and patch details below.

Woodpecker gRPC agent_id metadata can be spoofed- cross-tenant agent impersonation

Also known asCVE-2026-50141GO-2026-5976

Published

Jul 14, 2026

Updated

Jul 21, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 28, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-g7mm-9vx7-jm7h.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs35th percentile — riskier than 35% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹go.woodpecker-ci.org/woodpecker/v3

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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

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 (WOODPECKER_DISABLE_USER_AGENT_REGISTRATION=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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`go.woodpecker-ci.org/woodpecker/v3`	≥ 3.0.0&&< 3.14.1	3.14.1`go get go.woodpecker-ci.org/woodpecker/v3@v3.14.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for go.woodpecker-ci.org/woodpecker/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update go.woodpecker-ci.org/woodpecker/v3 to 3.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g7mm-9vx7-jm7h is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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 `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. ### 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 (`WOODPECKER_DISABLE_USER_AGENT_REGISTRATION=true`) and delete existing on

O3 Security · Impact-Aware SCA

Is GHSA-g7mm-9vx7-jm7h in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works