GHSA-3wf2-2pq4-4rvc is a high-severity (CVSS 7.5) CWE-74 vulnerability in go.woodpecker-ci.org/woodpecker/v2. O3 Security confirms whether GHSA-3wf2-2pq4-4rvc is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Woodpecker's custom environment variables allow to alter execution flow of plugins
Real-World Exposure
go.woodpecker-ci.org/woodpecker/v2🐹go.woodpecker-ci.org/woodpeckerReal-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
The server allow to create any user who can trigger a pipeline run malicious workflows:
- Those workflows can either lead to a host takeover that runs the agent executing the workflow.
- Or allow to extract the secrets who would be normally provided to the plugins who's entrypoint are overwritten.
Patches
https://github.com/woodpecker-ci/woodpecker/pull/3909 https://github.com/woodpecker-ci/woodpecker/pull/3934
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading? Enable the "gated" repo feature and review each change upfront of running
References
- https://github.com/woodpecker-ci/woodpecker/pull/3909
- https://github.com/woodpecker-ci/woodpecker/pull/3934
- https://github.com/woodpecker-ci/woodpecker-security/issues/10 (info will be published later at https://github.com/woodpecker-ci/woodpecker/issues/3929)
- https://github.com/woodpecker-ci/woodpecker/issues/3929 (info will be published later once we got adoption of the update)
Credits
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | go.woodpecker-ci.org/woodpecker/v2 | all versions | 2.7.0 |
| 🐹Go | go.woodpecker-ci.org/woodpecker | all versions | 2.7.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for go.woodpecker-ci.org/woodpecker/v2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update go.woodpecker-ci.org/woodpecker/v2 to 2.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3wf2-2pq4-4rvc 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.
How O3 protects you
O3 pinpoints whether GHSA-3wf2-2pq4-4rvc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-3wf2-2pq4-4rvc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-3wf2-2pq4-4rvc in your dependencies?
O3 detects GHSA-3wf2-2pq4-4rvc across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.